Android™

WebSocket Connect

See more WebSocket Examples

Demonstrates how to establish a WebSocket connection. Once the connection is established, messages may be sent back-and-forth. Messages are sent in frames, where the last frame in the message is indicated by a "final" bit. A frame constitutes the entire message if the first frame sent has the "final" bit sent. (In most cases, you'll probably be sending single-frame messages.) Android™

// 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;

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

    //  --------------------------------------------------
    //  A WebSocket connection begins life as an HTTP GET request containing a few special header fields,
    //  such as "Upgrade: websocket".   

    //  Your application will use the Chilkat Rest class to send the initial HTTP GET.  This allows you
    //  to use the full capability of the Chilkat Rest class to customize the GET for any particular situation.
    //  For example:
    //  
    //    - If custom HTTP request header fields must be added.
    //    - If authentication is required, such as OAuth2, OAuth1, Basic HTTP Auth, etc.
    //    - If HTTPS, SSH Tunneling, Proxies (HTTP or SOCKS), or other advanced connection or TLS features are required.
    //  

    CkRest rest = new CkRest();
    success = rest.Connect("someserver.com",80,false,false);
    if (success != true) {
        Log.i(TAG, rest.lastErrorText());
        return;
        }

    CkWebSocket ws = new CkWebSocket();

    //  Tell the WebSocket to use this connection.
    success = ws.UseConnection(rest);
    if (success != true) {
        Log.i(TAG, ws.lastErrorText());
        return;
        }

    //  Add the standard WebSocket open handshake headers that will be needed.
    //  (This adds the required HTTP request headers to the rest object.)
    ws.AddClientHeaders();

    //  Add any additional headers that might be desired.
    //  Two common WebSocketSpecific headers are "Sec-WebSocket-Protocol" and "Origin".
    rest.AddHeader("Sec-WebSocket-Protocol","x-something");
    rest.AddHeader("Origin","http://someserver.com");

    //  Do the open handshake.
    String responseBody = rest.fullRequestNoBody("GET","/something");
    if (rest.get_LastMethodSuccess() != true) {
        Log.i(TAG, rest.lastErrorText());
        return;
        }

    //  If successful, the HTTP response status code should be 101,
    //  and the response body will be empty. (If it failed, we'll have a look
    //  at the response body..)
    int statusCode = rest.get_ResponseStatusCode();
    Log.i(TAG, "Response status code: " + String.valueOf(statusCode));

    if (statusCode != 101) {
        Log.i(TAG, responseBody);
        Log.i(TAG, "-- Failed because of unexpected response status code.");
        return;
        }

    //  We have the expected 101 response, so let's now validate the 
    //  contents of the response, such as the value sent by the server in the
    //  Sec-WebSocket-Accept header. 
    success = ws.ValidateServerHandshake();
    if (success != true) {
        Log.i(TAG, ws.lastErrorText());
        return;
        }

    Log.i(TAG, "WebSocket connection successful.");

    //  The application may now begin sending and receiving frames on the WebSocket connection.
    //  (At this point, we're done with the rest object...)

  }

  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."
  }
}