provides a factory class which utilizes javax.net.SocketFactory interface,
provides a rich listener interface to hook web socket events,
has fine-grained error codes for fine-grained controllability on errors,
allows to disable validity checks on RSV1/RSV2/RSV3 bits and opcode of frames.
supports HTTP proxy, especially "Secure WebSocket" (wss) through "Secure Proxy" (https),
and supports RFC 7692 (Compression Extensions for WebSocket), also known as permessage-deflate extension (not enabled by default).
Description
Create WebSocketFactory
WebSocketFactory is a factory class that creates WebSocket instances. The
first step is to create a WebSocketFactory instance.
// Create a WebSocketFactory instance.
WebSocketFactory factory = new WebSocketFactory();
By default, WebSocketFactory uses SocketFactory.getDefault() for non-secure
WebSocket connections (ws:) and SSLSocketFactory.getDefault() for secure
WebSocket connections (wss:). You can change this default behavior by using
WebSocketFactory.setSocketFactory method, WebSocketFactory.setSSLSocketFactory
method and WebSocketFactory.setSSLContext method. Note that you don't have to call a setSSL* method at all if you use the default SSL configuration. Also note that calling setSSLSocketFactory method has not meaning if you have called setSSLContext method. See the description of WebSocketFactory.createSocket(URI) method for details.
The following is an example
to set a custom SSL context to a WebSocketFactory instance. (Again, you don't have to call a setSSL* method if you use the default SSL configuration.)
// Create a custom SSL context.
SSLContext context = NaiveSSLContext.getInstance("TLS");
// Set the custom SSL context.
factory.setSSLContext(context);
NativeSSLContext
used in the above example is a factory class to create an SSLContext which
naively accepts all certificates without verification. It's enough for testing
purposes. When you see an error message "unable to find valid certificate path
to requested target" while testing, try NaiveSSLContext.
HTTP Proxy
If a WebSocket endpoint needs to be accessed via an HTTP proxy, information
about the proxy server has to be set to a WebSocketFactory instance before
creating a WebSocket instance. Proxy settings are represented by
ProxySettings class. A WebSocketFactory instance has an associated
ProxySettings instance and it can be obtained by calling
WebSocketFactory.getProxySettings() method.
// Get the associated ProxySettings instance.
ProxySettings settings = factory.getProxySettings();
ProxySettings class has methods to set information about a proxy server such
as setHost method and setPort method. The following is an example to set a
secure (https) proxy server.
// Set a proxy server.
settings.setServer("https://proxy.example.com");
If credentials are required for authentication at a proxy server, setId
method and setPassword method, or setCredentials method can be used to set
the credentials. Note that, however, the current implementation supports only
Basic Authentication.
// Set credentials for authentication at a proxy server.
settings.setCredentials(id, password);
Create WebSocket
WebSocket class represents a web socket. Its instances are created by calling one of createSocket methods of a WebSocketFactory instance. Below is the simplest example to create a WebSocket instance.
// Create a web socket. The scheme part can be one of
// the following: 'ws', 'wss', 'http' and 'https'
// (case-insensitive). The user info part, if any, is
// interpreted as expected. If a raw socket failed to
// be created, of if HTTP proxy handshake or SSL
// handshake failed, an IOException is thrown.
WebSocket ws = new WebSocketFactory()
.createSocket("ws://localhost/endpoint");
There are two ways to set a timeout value for socket connection. The first way is to call setConnectionTimeout(int timeout) method of WebSocketFactory.
// Create a web socket factory and set 5000 milliseconds
// as a timeout value for socket connection.
WebSocketFactory factory
= new WebSocketFactory().setConnectionTimeout(5000);
// Create a web socket. The timeout value set above is used.
WebSocket ws
= factory.createSocket("ws://localhost/endpoint");
The other way is to give a timeout value to createSocket method.
// Create a web socket factory. The timeout value remains 0.
WebSocketFactory factory = new WebSocketFactory();
// Create a web socket with a socket connection timeout value.
WebSocket ws
= factory.createSocket("ws://localhost/endpoint", 5000);
The timeout value is passed to connect(SocketAddress, int) method of java.net.Socket.
Register Listener
After creating a WebSocket instance, you should call addListener method to register a WebSocketListener that receives web socket events. WebSocketAdapter is an empty implementation of WebSocketListener interface.
// Register a listener to receive web socket events.
ws.addListener(new WebSocketAdapter() {
@Override
public void onTextMessage(WebSocket websocket, String message)
throws Exception
{
// Received a text message.
......
}
});
Configure WebSocket
Before starting a WebSocket opening handshake with the server, you can configure the web socket instance by using the following methods.
METHOD
DESCRIPTION
addProtocol
Adds an element to Sec-WebSocket-Procotol.
addExtension
Adds an element to Sec-WebSocket-Extensions.
addHeader
Adds an arbitrary HTTP header.
setUserInfo
Adds Authorization header for Basic Authentication.
getSocket
Gets the underlying Socket instance to configure it.
setExtended
Disables validity checks on RSV1/RSV2/RSV3 and opcode.
setFrameQueueSize
Set the size of the frame queue for congestion control.
setMaxPayloadSize
Set the maximum payload size.
Note that permessage-defeflate extension (RFC 7692) has been supported since version 1.17. To enable the extension, call addExtension method with "permessage-deflate".
The permessage-deflate support is new and needs testing. Feedback is welcome.
Connect To Server
By calling connect() method, connection to the server is established and a WebSocket opening handshake is performed
synchronously. If an error occurred during the handshake, a WebSocketException would be thrown. Instead, if the handshake succeeds,
the connect() implementation creates threads and starts them to read and
write web socket frames asynchronously.
try
{
// Connect to the server and perform an opening handshake.
// This method blocks until the opening handshake is finished.
ws.connect();
}
catch (OpeningHandshakeException e)
{
// A violation against the WebSocket protocol was detected
// during the opening handshake.
}
catch (WebSocketException e)
{
// Failed to establish a WebSocket connection.
}
In some cases, connect() method throws OpeningHandshakeException which is a subclass of WebSocketException (since version 1.19). OpeningHandshakeException provides additional methods such as getStatusLine(), getHeaders() and getBody() to access the response from a server. The following snippet is an example to print information that the exception holds.
catch (OpeningHandshakeException e)
{
// Status line.
StatusLine sl = e.getStatusLine();
System.out.println("=== Status Line ===");
System.out.format("HTTP Version = %s\n", sl.getHttpVersion());
System.out.format("Status Code = %d\n", sl.getStatusCode());
System.out.format("Reason Phrase = %s\n", sl.getReasonPhrase());
// HTTP headers.
Map<String, List<String>> headers = e.getHeaders();
System.out.println("=== HTTP Headers ===");
for (Map.Entry<String, List<String>> entry : headers.entrySet())
{
// Header name.
String name = entry.getKey();
// Values of the header.
List<String> values = entry.getValue();
if (values == null || values.size() == 0)
{
// Print the name only.
System.out.println(name);
continue;
}
for (String value : values)
{
// Print the name and the value.
System.out.format("%s: %s\n", name, value);
}
}
}
Connect To Server Asynchronously
The simplest way to call
connect()
method asynchronously is to use
connectAsynchronously()
method. The implementation of the method creates a thread and calls
connect()
method in the thread. When the
connect()
call failed,
onConnectError()
of
WebSocketListener
would be called. Note that
onConnectError()
is called only when
connectAsynchronously()
was used and the
connect()
call executed in the background thread failed. Neither direct synchronous
connect()
nor
connect(ExecutorService)
(described below) will trigger the callback method.
// Connect to the server asynchronously.
ws.connectAsynchronously();
Another way to call
connect(ExecutorService)
method asynchronously is to use
connect(ExecutorService)
method. The method performs a WebSocket opening handshake asynchronously using the given
ExecutorService.
// Prepare an ExecutorService.
ExecutorService es = Executors.newSingleThreadExecutor();
// Connect to the server asynchronously.
Future<WebSocket> future = ws.connect(es);
try
{
// Wait for the opening handshake to complete.
future.get();
}
catch (ExecutionException e)
{
if (e.getCause() instanceof WebSocketException)
{
......
}
}
The implementation of
connect(ExecutorService)
method creates a
Callable<WebSocket>
instance by calling
connectable()
method and passes the instance to
submit(Callable)
method of the given
ExecutorService.
What the implementation of
call()
method of the
Callable
instance does is just to call the synchronous
connect().
Send Frames
Web socket frames can be sent by sendFrame method. Other sendXxx
methods such as sendText are aliases of sendFrame method. All of
the sendXxx methods work asynchronously. However, under some conditions, sendXxx methods may block. See Congestion Control for details.
Below are some examples
of sendXxx methods. Note that in normal cases, you don't have to
call sendClose method and sendPong method (or their variants)
explicitly because they are called automatically when appropriate.
// Send a text frame.
ws.sendText("Hello.");
// Send a binary frame.
byte[] binary = ......;
ws.sendBinary(binary);
// Send a ping frame.
ws.sendPing("Are you there?");
If you want to send fragmented frames, you have to know the details of the
specification (5.4. Fragmentation).
Below is an example to send a text message ("How are you?") which consists
of 3 fragmented frames.
// The first frame must be either a text frame or
// a binary frame. And its FIN bit must be cleared.
WebSocketFrame firstFrame = WebSocketFrame
.createTextFrame("How ")
.setFin(false);
// Subsequent frames must be continuation frames. The FIN
// bit of all continuation frames except the last one must
// be cleared. Note that the FIN bit of frames returned
// from WebSocketFrame.createContinuationFrame() method
// is cleared, so the example below does not clear the
// FIN bit explicitly.
WebSocketFrame secondFrame = WebSocketFrame
.createContinuationFrame("are ");
// The last frame must be a continuation frame with the
// FIN bit set. Note that the FIN bit of frames returned
// from WebSocketFrame.createContinuationFrame methods
// is cleared, so the FIN bit of the last frame must be
// set explicitly.
WebSocketFrame lastFrame = WebSocketFrame
.createContinuationFrame("you?")
.setFin(true);
// Send a text message which consists of 3 frames.
ws.sendFrame(firstFrame)
.sendFrame(secondFrame)
.sendFrame(lastFrame);
Alternatively, the same as above can be done like this.
You can send ping frames periodically by calling setPingInterval method
with an interval in milliseconds between ping frames. This method can be
called both before and after connect() method. Passing zero stops the
periodical sending.
// Send a ping per 60 seconds.
ws.setPingInterval(60 * 1000);
// Stop the periodical sending.
ws.setPingInterval(0);
Likewise, you can send pong frames periodically by calling setPongInterval
method. "A Pong frame MAY be sent unsolicited." (RFC 6455, 5.5.3. Pong)
You can customize payload of ping/pong frames that are sent automatically by using setPingPayloadGenerator() and setPongPayloadGenerator() methods. Both methods take an instance of PayloadGenerator interface. the following is an example to use the string representation of the current date as payload of ping frames.
ws.setPingPayloadGenerator(new PayloadGenerator() {
@Override
public byte[] generate() {
// The string representation of the current date.
return new Date().toString().getBytes();
}
});
Note that the maximum payload length of control frames (e.g. ping frames) is 125. Therefore, the length of a byte array returned from generate() method must not exceed 125.
Auto Flush
By default, a frame is automatically flushed to the server immediately after
sendFrame
method is executed. This automatic flush can be disabled by calling
setAutoFlush(false).
// Disable auto-flush.
ws.setAutoFlush(false);
To flush frames manually, call
flush()
method. Note that this method works asynchronously.
// Flush frames to the server manually.
ws.flush();
Congestion Control
sendXxx methods queue a WebSocketFrame instance to the internal queue. By default, no upper limit is imposed on the queue size, so sendXxx methods do not block. However, this behavior may cause a problem if your WebSocket client application sends too many WebSocket frames in a short time for the WebSocket server to process. In such a case, you may want sendXxx methods to block when many frames are queued.
You can set an upper limit on the internal queue by calling setFrameQueueSize(int) method. As a result, if the number of frames in the queue has reached the upper limit when a sendXxx method is called, the method blocks until the queue gets spaces. The code snippet below is an example to set 5 as the upper limit of the internal frame queue.
// Set 5 as the frame queue size.
ws.setFrameQueueSize(5);
Note that under some conditions, even if the queue is full, sendXxx methods do not block. For example, in the case where the thread to send frames (WritingThread) is going to stop or has already stopped. In addition, method calls to send a control frame (e.g. sendClose() and sendPing()) do not block.
Maximum Payload Size
You can set an upper limit on the payload size of WebSocket frames by calling setMaxPayloadSize(int) method with a positive value. Text, binary and continuation frames whose payload size is bigger than the maximum payload size you have set will be split into multiple frames.
// Set 1024 as the maximum payload size.
ws.setMaxPayloadSize(1024);
Control frames (close, ping and pong frames) are never split as per the specification.
If permessage-deflate extension is enabled and if the payload size of a WebSocket frame after compression does not exceed the maximum payload size, the WebSocket frame is not split even if the payload size before compression exceeds the maximum payload size.
Disconnect WebSocket
Before a web socket is closed, a closing handshake is performed. A closing
handshake is started (1) when the server sends a close frame to the client
or (2) when the client sends a close frame to the server. You can start a
closing handshake by calling disconnect() method (or by sending a close
frame manually).
// Close the web socket connection.
ws.disconnect();
disconnect() method has some variants. If you want to change the close code
and the reason phrase of the close frame that this client will send to the
server, use a variant method such as disconnect(int, String). disconnect()
itself is an alias of disconnect(WebSocketCloseCode.NORMAL, null).
Reconnection
WebSocket.connect() method can be called at most only once regardless of
whether the method succeeded or failed. If you want to re-connect to the
WebSocket endpoint, you have to create a new WebSocket instance again by
calling one of createSocket methods of a WebSocketFactory.
You may find
recreate() method useful if you want to create a new WebSocket instance
that has the same settings as the original instance. Note that, however,
settings you made on the raw socket of the original WebSocket instance
are not copied.
// Create a new WebSocket instance and connect to the same endpoint.
ws = ws.recreate().connect();
There is a variant of recreate() method that takes a timeout value for socket connection. If you want to use a timeout value that is different from the one used when the existing WebSocket instance was created, use recreate(int timeout) method.
Error Handling
WebSocketListener has some onXxxError() methods such as onFrameError() and onSendError(). Among such methods, onError() is a special one. It is always called before any other onXxxError() is called. For example, in the implementation of run() method of ReadingThread, Throwable is caught and onError() and onUnexpectedError() are called in this order. The following is the implementation.
@Override
public void run()
{
try
{
main();
}
catch (Throwable t)
{
// An uncaught throwable was detected in the reading thread.
WebSocketException cause = new WebSocketException(
WebSocketError.UNEXPECTED_ERROR_IN_READING_THREAD,
"An uncaught throwable was detected in the reading thread", t);
// Notify the listeners.
ListenerManager manager = mWebSocket.getListenerManager();
manager.callOnError(cause);
manager.callOnUnexpectedError(cause);
}
}
So, you can handle all error cases in onError() method.
All onXxxError() methods receive a WebSocketException instance as the second argument (the first argument is a WebSocket instance). The exception class provides getError() method which returns a WebSocketError enum entry. Entries in WebSocketError enum are possible causes of errors that may occur in the implementation of this library. The error causes are so granular that they can make it easy for you to find the root cause when an error occurs.
Throwables thrown by implementations of onXxx() callback methods are passed to handleCallbackError() of WebSocketListener.
@Override
public void handleCallbackError(WebSocket websocket, Throwable cause)
throws Exception {
// Throwables thrown by onXxx() callback methods come here.
}
Sample Application
The following is a sample application that connects to the echo server on
websocket.org (ws://echo.websocket.org) and
repeats to (1) read a line from the standard input, (2) send the read line
to the server and (3) prints the response from the server, until exit is
entered. The source code can be downloaded from Gist.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
