Sample code for 30+ languages & platforms
React Native

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.

Chilkat React Native Downloads

React Native
import { Socket, StringBuilder } from '@chilkat/react-native'

async function chilkatExample() {
  // This example assumes the Chilkat API to have been previously unlocked.
  // See Global Unlock Sample for sample code.

  const socket = new Socket();

  const tls = false;
  const maxWaitMs = 20000;
  const domainOrIpAddr = 'example.com';
  const port = 1234;

  // Connect to the whatever is expecting our connection...
  try {
    await socket.connectAsync(domainOrIpAddr, port, tls, maxWaitMs);
  } catch {
    console.log(socket.lastErrorText);
    return;
  }

  // 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..
  const sbXml = new StringBuilder();
  try {
    sbXml.loadFile('qa_data/xml/myUtf16.xml', 'utf-16');
  } catch {
    console.log('Failed to load utf-16 XML file..');
    return;
  }

  // Tell the socket object that we wish to send the utf-16 byte representation of the string.
  socket.stringCharset = 'utf-16';

  // Send the string as utf-16 bytes.
  try {
    await socket.sendSbAsync(sbXml);
  } catch {
    console.log(socket.lastErrorText);
    return;
  }

  // Let's say we wanted to instead send the string as utf-8 bytes.
  // Just tell the socket object...
  socket.stringCharset = 'utf-8';

  // Send the string as utf-8 bytes.
  try {
    await socket.sendSbAsync(sbXml);
  } catch {
    console.log(socket.lastErrorText);
    return;
  }

  // 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).
  try {
    sbXml.loadFile('qa_data/xml/myUtf8.xml', 'utf-8');
  } catch {
    console.log('Failed to load utf-8 XML file..');
    return;
  }

  // Send as utf-16
  socket.stringCharset = 'utf-16';

  // Send the string as utf-16 bytes.
  try {
    await socket.sendSbAsync(sbXml);
  } catch {
    console.log(socket.lastErrorText);
    return;
  }

  // ...
  // ...
}