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.

// Important: Don't forget to include the call to System.loadLibrary
// as shown at the bottom of this code sample.
package com.test;

import android.app.Activity;
import com.chilkatsoft.*;

import android.widget.TextView;
import android.os.Bundle;

public class SimpleActivity extends Activity {

  private static final String TAG = "Chilkat";

  // Called when the activity is first created.
  @Override
  public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);

    boolean success = false;

    CkSocket socket = new CkSocket();

    //  Connect to the server using TLS.
    boolean bTls = true;
    int maxWaitMs = 5000;
    success = socket.Connect("example.com",5000,bTls,maxWaitMs);
    if (success == false) {
        Log.i(TAG, socket.lastErrorText());
        return;
        }

    //  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.
    socket.put_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.
    String hex = socket.receiveNBytesENC(16,"hex");
    if (socket.get_LastMethodSuccess() == false) {
        Log.i(TAG, socket.lastErrorText());
        return;
        }

    Log.i(TAG, hex);

  }

  static {
      System.loadLibrary("chilkat");

      // Note: If the incorrect library name is passed to System.loadLibrary,
      // then you will see the following error message at application startup:
      //"The application <your-application-name> has stopped unexpectedly. Please try again."
  }
}