Tcl

Send UTF-16 on TCP or TLS Socket

See more Socket/SSL/TLS Examples

Demonstrates how to send a string on a connected TCP or SSL/TLS socket such that it is the utf-16 byte representation that is sent. Tcl

load ./chilkat.dll

set success 0

# This example assumes the Chilkat API to have been previously unlocked.
# See Global Unlock Sample for sample code.

set socket [new_CkSocket]

set tls 0
set maxWaitMs 20000
set domainOrIpAddr "example.com"
set port 1234

# Connect to the whatever is expecting our connection...
set success [CkSocket_Connect $socket $domainOrIpAddr $port $tls $maxWaitMs]
if {$success != 1} then {
    puts [CkSocket_lastErrorText $socket]
    delete_CkSocket $socket
    exit
}

# Let's say we have an XML file saved in the utf-16 byte representation,
# and we want to send it over the connection using the utf-16 byte representation...

# First the file into a Chilkat StringBuilder.
# Tell the LoadFile method that we are reading utf-16 bytes..
set sbXml [new_CkStringBuilder]

set success [CkStringBuilder_LoadFile $sbXml "qa_data/xml/myUtf16.xml" "utf-16"]
if {$success != 1} then {
    puts "Failed to load utf-16 XML file.."
    delete_CkSocket $socket
    delete_CkStringBuilder $sbXml
    exit
}

# Tell the socket object that we wish to send the utf-16 byte representation of the string.
CkSocket_put_StringCharset $socket "utf-16"

# Send the string as utf-16 bytes.
set success [CkSocket_SendSb $socket $sbXml]
if {$success != 1} then {
    puts [CkSocket_lastErrorText $socket]
    delete_CkSocket $socket
    delete_CkStringBuilder $sbXml
    exit
}

# Let's say we wanted to instead send the string as utf-8 bytes.
# Just tell the socket object...
CkSocket_put_StringCharset $socket "utf-8"

# Send the string as utf-8 bytes.
set success [CkSocket_SendSb $socket $sbXml]
if {$success != 1} then {
    puts [CkSocket_lastErrorText $socket]
    delete_CkSocket $socket
    delete_CkStringBuilder $sbXml
    exit
}

# If our XML file was utf-8, then just tell the StringBuilder that we're reading utf-8.
# Once the text is properly contained in the StringBuilder, we can send the contents in any other charset (windows-1252, utf-16, utf-8, etc.) 
# as long as it make sense (i.e. we obviously can't send Japanese text using a single-byte charset such as Windows-1252).
set success [CkStringBuilder_LoadFile $sbXml "qa_data/xml/myUtf8.xml" "utf-8"]
if {$success != 1} then {
    puts "Failed to load utf-8 XML file.."
    delete_CkSocket $socket
    delete_CkStringBuilder $sbXml
    exit
}

# Send as utf-16
CkSocket_put_StringCharset $socket "utf-16"

# Send the string as utf-16 bytes.
set success [CkSocket_SendSb $socket $sbXml]
if {$success != 1} then {
    puts [CkSocket_lastErrorText $socket]
    delete_CkSocket $socket
    delete_CkStringBuilder $sbXml
    exit
}

# ...
# ...

delete_CkSocket $socket
delete_CkStringBuilder $sbXml