Xbase++
Xbase++
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 Xbase++ Downloads
LOCAL nSuccess
LOCAL oSocket
LOCAL nBTls
LOCAL nMaxWaitMs
LOCAL cHex
nSuccess := 0
oSocket := CreateObject("Chilkat.Socket")
// Connect to the server using TLS.
nBTls := 1
nMaxWaitMs := 5000
nSuccess := oSocket:Connect("example.com", 5000, nBTls, nMaxWaitMs)
IF (nSuccess == 0)
? oSocket:LastErrorText
oSocket:destroy()
RETURN
ENDIF
// 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.
oSocket: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.
cHex := oSocket:ReceiveNBytesENC(16, "hex")
IF (oSocket:LastMethodSuccess == 0)
? oSocket:LastErrorText
oSocket:destroy()
RETURN
ENDIF
? cHex
oSocket:destroy()