PowerBuilder
PowerBuilder
Receive an Exact Number of Bytes as Encoded Text
See more Socket/SSL/TLS Examples
Demonstrates Socket.ReceiveNBytesENC, which receives exactly the requested number of bytes and returns them encoded using a named encoding. It waits until the full count is received.
Background. Inactivity is controlled by
MaxReadIdleMs: the call fails if incoming bytes halt for longer than MaxReadIdleMs milliseconds before the full amount is received. The ENC methods move raw binary data to and from printable text using a named encoding such as base64 or hex.Chilkat PowerBuilder Downloads
integer li_rc
integer li_Success
oleobject loo_Socket
integer li_BTls
integer li_MaxWaitMs
string ls_Hex
li_Success = 0
loo_Socket = create oleobject
li_rc = loo_Socket.ConnectToNewObject("Chilkat.Socket")
if li_rc < 0 then
destroy loo_Socket
MessageBox("Error","Connecting to COM object failed")
return
end if
// Connect to the server using TLS.
li_BTls = 1
li_MaxWaitMs = 5000
li_Success = loo_Socket.Connect("example.com",5000,li_BTls,li_MaxWaitMs)
if li_Success = 0 then
Write-Debug loo_Socket.LastErrorText
destroy loo_Socket
return
end if
// MaxReadIdleMs controls the inactivity limit for receiving. The ReceiveNBytesENC call will fail if
// incoming bytes halt for longer than this many milliseconds before the full amount is received.
loo_Socket.MaxReadIdleMs = 15000
// Receive exactly the requested number of bytes and return them encoded using the named encoding.
// Unlike ReceiveBytesENC, this waits until the full count has been received.
ls_Hex = loo_Socket.ReceiveNBytesENC(16,"hex")
if loo_Socket.LastMethodSuccess = 0 then
Write-Debug loo_Socket.LastErrorText
destroy loo_Socket
return
end if
Write-Debug ls_Hex
destroy loo_Socket