Android™
Android™
Receive a 32-bit Integer from a Socket
See more Socket/SSL/TLS Examples
Demonstrates Socket.ReceiveInt32, which reads exactly four bytes as a signed 32-bit integer and stores the result in the ReceivedInt property. Byte order is selectable.
Background. Fixed-size integers and length prefixes are common building blocks for application-defined binary protocols. Byte order is selectable, with big-endian being network byte order.
Chilkat Android™ Downloads
// 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;
}
// Read exactly four bytes as a signed 32-bit integer and store the result in the ReceivedInt
// property. The argument selects byte order (true = big-endian, network byte order).
boolean bBigEndian = true;
success = socket.ReceiveInt32(bBigEndian);
if (success == false) {
Log.i(TAG, socket.lastErrorText());
return;
}
Log.i(TAG, "Received 32-bit integer: " + String.valueOf(socket.get_ReceivedInt()));
}
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."
}
}