Xbase++

Receive a String from a Socket

Demonstrates Socket.ReceiveString, which receives text and decodes it using StringCharset. It returns the first nonempty decoded result rather than draining all available data.

Background. Text send and receive operations encode and decode bytes using the StringCharset property. For plain ASCII or UTF-8 protocols, setting StringCharset to utf-8 is a safe default.

Chilkat Xbase++ Downloads

Download Chilkat for Xbase++

Xbase++

LOCAL nSuccess
LOCAL oSocket
LOCAL nBTls
LOCAL nMaxWaitMs
LOCAL cCommand
LOCAL cResponseText

nSuccess := 0

oSocket := CreateObject("Chilkat.Socket")

//  Connect to the server using TLS.  The 3rd argument enables the TLS handshake after the TCP
//  connection succeeds; the 4th is the maximum time to wait, in milliseconds.
nBTls := 1
nMaxWaitMs := 5000
nSuccess := oSocket:Connect("example.com", 5000, nBTls, nMaxWaitMs)
IF (nSuccess == 0)
    ? oSocket:LastErrorText
    oSocket:destroy()
    RETURN
ENDIF

//  StringCharset controls the character encoding used when sending and receiving text.
oSocket:StringCharset := "utf-8"
//  Send a request using a simple application-defined text protocol in which each message ends with a
//  CRLF.
cCommand := "STATUS" + Chr(13) + Chr(10)
nSuccess := oSocket:SendString(cCommand)
IF (nSuccess == 0)
    ? oSocket:LastErrorText
    oSocket:destroy()
    RETURN
ENDIF

//  Receive text and decode it using StringCharset.  ReceiveString returns the first nonempty decoded
//  result; it does not keep reading to drain all available data.
cResponseText := oSocket:ReceiveString()
IF (oSocket:LastMethodSuccess == 0)
    ? oSocket:LastErrorText
    oSocket:destroy()
    RETURN
ENDIF

? cResponseText

oSocket:destroy()