Package io.vertx.core.http
Interface ClientWebSocket
-
- All Superinterfaces:
ReadStream<Buffer>
,StreamBase
,WebSocket
,WebSocketBase
,WriteStream<Buffer>
public interface ClientWebSocket extends WebSocket
Represents a client-side WebSocket.- Author:
- Tim Fox
-
-
Method Summary
All Methods Instance Methods Abstract Methods Default Methods Modifier and Type Method Description ClientWebSocket
binaryMessageHandler(Handler<Buffer> handler)
Set a binary message handler on the connection.ClientWebSocket
closeHandler(Handler<Void> handler)
Set a close handler.default Future<WebSocket>
connect(int port, String host, String requestURI)
Connect this WebSocket to the specified port, host and relative request URI.Future<WebSocket>
connect(WebSocketConnectOptions options)
Connect this WebSocket with the specified options.default Future<WebSocket>
connect(String requestURI)
Connect this WebSocket at the relative request URI using the default host and port.default Future<WebSocket>
connect(String host, String requestURI)
Connect this WebSocket to the host and relative request URI and default port.ClientWebSocket
drainHandler(Handler<Void> handler)
Set a drain handler on the stream.ClientWebSocket
endHandler(Handler<Void> endHandler)
Set an end handler.ClientWebSocket
exceptionHandler(Handler<Throwable> handler)
Set an exception handler on the read stream.ClientWebSocket
fetch(long amount)
Fetch the specifiedamount
of elements.ClientWebSocket
frameHandler(Handler<WebSocketFrame> handler)
Set a frame handler on the connection.ClientWebSocket
handler(Handler<Buffer> handler)
Set a data handler.ClientWebSocket
pause()
Pause theReadStream
, it sets the buffer infetch
mode and clears the actual demand.ClientWebSocket
pongHandler(Handler<Buffer> handler)
Set a pong frame handler on the connection.default ClientWebSocket
resume()
Resume reading, and sets the buffer inflowing
mode.ClientWebSocket
setWriteQueueMaxSize(int maxSize)
Set the maximum size of the write queue tomaxSize
.ClientWebSocket
textMessageHandler(Handler<String> handler)
Set a text message handler on the connection.-
Methods inherited from interface io.vertx.core.streams.ReadStream
collect, pipe, pipeTo
-
Methods inherited from interface io.vertx.core.http.WebSocket
shutdownHandler
-
Methods inherited from interface io.vertx.core.http.WebSocketBase
binaryHandlerID, close, close, close, closeReason, closeStatusCode, end, headers, isClosed, isSsl, localAddress, peerCertificates, remoteAddress, shutdown, shutdown, shutdown, shutdown, shutdown, shutdown, sslSession, subProtocol, textHandlerID, writeBinaryMessage, writeFinalBinaryFrame, writeFinalTextFrame, writeFrame, writePing, writePong, writeTextMessage
-
Methods inherited from interface io.vertx.core.streams.WriteStream
end, write, writeQueueFull
-
-
-
-
Method Detail
-
connect
Future<WebSocket> connect(WebSocketConnectOptions options)
Connect this WebSocket with the specified options.- Parameters:
options
- the request options- Returns:
- a future notified when the WebSocket when connected
-
connect
default Future<WebSocket> connect(int port, String host, String requestURI)
Connect this WebSocket to the specified port, host and relative request URI.- Parameters:
port
- the porthost
- the hostrequestURI
- the relative URI- Returns:
- a future notified when the WebSocket when connected
-
connect
default Future<WebSocket> connect(String host, String requestURI)
Connect this WebSocket to the host and relative request URI and default port.- Parameters:
host
- the hostrequestURI
- the relative URI- Returns:
- a future notified when the WebSocket when connected
-
connect
default Future<WebSocket> connect(String requestURI)
Connect this WebSocket at the relative request URI using the default host and port.- Parameters:
requestURI
- the relative URI- Returns:
- a future notified when the WebSocket when connected
-
pause
ClientWebSocket pause()
Description copied from interface:ReadStream
Pause theReadStream
, it sets the buffer infetch
mode and clears the actual demand.While it's paused, no data will be sent to the data
handler
.- Specified by:
pause
in interfaceReadStream<Buffer>
- Specified by:
pause
in interfaceWebSocket
- Specified by:
pause
in interfaceWebSocketBase
- Returns:
- a reference to this, so the API can be used fluently
-
resume
default ClientWebSocket resume()
Description copied from interface:ReadStream
Resume reading, and sets the buffer inflowing
mode. If theReadStream
has been paused, reading will recommence on it.- Specified by:
resume
in interfaceReadStream<Buffer>
- Specified by:
resume
in interfaceWebSocket
- Specified by:
resume
in interfaceWebSocketBase
- Returns:
- a reference to this, so the API can be used fluently
-
fetch
ClientWebSocket fetch(long amount)
Description copied from interface:ReadStream
Fetch the specifiedamount
of elements. If theReadStream
has been paused, reading will recommence with the specifiedamount
of items, otherwise the specifiedamount
will be added to the current stream demand.- Specified by:
fetch
in interfaceReadStream<Buffer>
- Specified by:
fetch
in interfaceWebSocket
- Specified by:
fetch
in interfaceWebSocketBase
- Returns:
- a reference to this, so the API can be used fluently
-
setWriteQueueMaxSize
ClientWebSocket setWriteQueueMaxSize(int maxSize)
Description copied from interface:WriteStream
Set the maximum size of the write queue tomaxSize
. You will still be able to write to the stream even if there is more thanmaxSize
items in the write queue. This is used as an indicator by classes such asPipe
to provide flow control. The value is defined by the implementation of the stream, e.g in bytes for aNetSocket
, etc...- Specified by:
setWriteQueueMaxSize
in interfaceWebSocket
- Specified by:
setWriteQueueMaxSize
in interfaceWebSocketBase
- Specified by:
setWriteQueueMaxSize
in interfaceWriteStream<Buffer>
- Parameters:
maxSize
- the max size of the write stream- Returns:
- a reference to this, so the API can be used fluently
-
handler
ClientWebSocket handler(Handler<Buffer> handler)
Description copied from interface:ReadStream
Set a data handler. As data is read, the handler will be called with the data.- Specified by:
handler
in interfaceReadStream<Buffer>
- Specified by:
handler
in interfaceWebSocket
- Specified by:
handler
in interfaceWebSocketBase
- Returns:
- a reference to this, so the API can be used fluently
-
endHandler
ClientWebSocket endHandler(Handler<Void> endHandler)
Description copied from interface:ReadStream
Set an end handler. Once the stream has ended, and there is no more data to be read, this handler will be called.- Specified by:
endHandler
in interfaceReadStream<Buffer>
- Specified by:
endHandler
in interfaceWebSocket
- Specified by:
endHandler
in interfaceWebSocketBase
- Returns:
- a reference to this, so the API can be used fluently
-
drainHandler
ClientWebSocket drainHandler(Handler<Void> handler)
Description copied from interface:WriteStream
Set a drain handler on the stream. If the write queue is full, then the handler will be called when the write queue is ready to accept buffers again. SeePipe
for an example of this being used.The stream implementation defines when the drain handler, for example it could be when the queue size has been reduced to
maxSize / 2
.- Specified by:
drainHandler
in interfaceWebSocket
- Specified by:
drainHandler
in interfaceWebSocketBase
- Specified by:
drainHandler
in interfaceWriteStream<Buffer>
- Parameters:
handler
- the handler- Returns:
- a reference to this, so the API can be used fluently
-
closeHandler
ClientWebSocket closeHandler(Handler<Void> handler)
Description copied from interface:WebSocketBase
Set a close handler. This will be called when the WebSocket is closed. After this callback, no more messages are expected. When the WebSocket received a close frame, theWebSocketBase.closeStatusCode()
will return the status code andWebSocketBase.closeReason()
will return the reason.- Specified by:
closeHandler
in interfaceWebSocket
- Specified by:
closeHandler
in interfaceWebSocketBase
- Parameters:
handler
- the handler- Returns:
- a reference to this, so the API can be used fluently
-
frameHandler
ClientWebSocket frameHandler(Handler<WebSocketFrame> handler)
Description copied from interface:WebSocketBase
Set a frame handler on the connection. This handler will be called when frames are read on the connection.- Specified by:
frameHandler
in interfaceWebSocket
- Specified by:
frameHandler
in interfaceWebSocketBase
- Parameters:
handler
- the handler- Returns:
- a reference to this, so the API can be used fluently
-
textMessageHandler
ClientWebSocket textMessageHandler(Handler<String> handler)
Description copied from interface:WebSocketBase
Set a text message handler on the connection. This handler will be called similar to theWebSocketBase.binaryMessageHandler(Handler)
, but the buffer will be converted to a String first- Specified by:
textMessageHandler
in interfaceWebSocket
- Specified by:
textMessageHandler
in interfaceWebSocketBase
- Parameters:
handler
- the handler- Returns:
- a reference to this, so the API can be used fluently
-
binaryMessageHandler
ClientWebSocket binaryMessageHandler(Handler<Buffer> handler)
Description copied from interface:WebSocketBase
Set a binary message handler on the connection. This handler serves a similar purpose toWebSocketBase.handler(Handler)
except that if a message comes into the socket in multiple frames, the data from the frames will be aggregated into a single buffer before calling the handler (usingWebSocketFrame.isFinal()
to find the boundaries).- Specified by:
binaryMessageHandler
in interfaceWebSocket
- Specified by:
binaryMessageHandler
in interfaceWebSocketBase
- Parameters:
handler
- the handler- Returns:
- a reference to this, so the API can be used fluently
-
pongHandler
ClientWebSocket pongHandler(Handler<Buffer> handler)
Description copied from interface:WebSocketBase
Set a pong frame handler on the connection. This handler will be invoked every time a pong frame is received on the server, and can be used by both clients and servers since the RFC 6455 section 5.5.2 and section 5.5.3 do not specify whether the client or server sends a ping.Pong frames may be at most 125 bytes (octets).
There is no ping handler since ping frames should immediately be responded to with a pong frame with identical content
Pong frames may be received unsolicited.
- Specified by:
pongHandler
in interfaceWebSocket
- Specified by:
pongHandler
in interfaceWebSocketBase
- Parameters:
handler
- the handler- Returns:
- a reference to this, so the API can be used fluently
-
exceptionHandler
ClientWebSocket exceptionHandler(Handler<Throwable> handler)
Description copied from interface:ReadStream
Set an exception handler on the read stream.- Specified by:
exceptionHandler
in interfaceReadStream<Buffer>
- Specified by:
exceptionHandler
in interfaceStreamBase
- Specified by:
exceptionHandler
in interfaceWebSocket
- Specified by:
exceptionHandler
in interfaceWebSocketBase
- Specified by:
exceptionHandler
in interfaceWriteStream<Buffer>
- Parameters:
handler
- the exception handler- Returns:
- a reference to this, so the API can be used fluently
-
-