DataFlex
DataFlex
Send a String over a Socket
See more Socket/SSL/TLS Examples
Demonstrates Socket.SendString, which encodes a string using StringCharset and sends the resulting bytes over the connected socket. No delimiter, terminator, or length prefix is added.
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 DataFlex Downloads
Use ChilkatAx-win32.pkg
Procedure Test
Boolean iSuccess
Handle hoSocket
Boolean iBTls
Integer iMaxWaitMs
String sMessage
String sTemp1
Move False To iSuccess
Get Create (RefClass(cComChilkatSocket)) To hoSocket
If (Not(IsComObjectCreated(hoSocket))) Begin
Send CreateComObject of hoSocket
End
// 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.
Move True To iBTls
Move 5000 To iMaxWaitMs
Get ComConnect Of hoSocket "example.com" 5000 iBTls iMaxWaitMs To iSuccess
If (iSuccess = False) Begin
Get ComLastErrorText Of hoSocket To sTemp1
Showln sTemp1
Procedure_Return
End
// StringCharset controls the character encoding used when sending and receiving text.
Set ComStringCharset Of hoSocket To "utf-8"
// Encode the string using StringCharset and send the resulting bytes. No delimiter, terminator, or
// length prefix is added; the exact bytes are sent. This example sends a command for a simple
// application-defined text protocol.
Move "STATUS" + (character(13)) + (character(10)) To sMessage
Get ComSendString Of hoSocket sMessage To iSuccess
If (iSuccess = False) Begin
Get ComLastErrorText Of hoSocket To sTemp1
Showln sTemp1
Procedure_Return
End
Showln "Message sent."
End_Procedure