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 SummaryAll Methods Instance Methods Abstract Methods Default Methods Modifier and Type Method Description ClientWebSocketbinaryMessageHandler(Handler<Buffer> handler)Set a binary message handler on the connection.ClientWebSocketcloseHandler(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.ClientWebSocketdrainHandler(Handler<Void> handler)Set a drain handler on the stream.ClientWebSocketendHandler(Handler<Void> endHandler)Set an end handler.ClientWebSocketexceptionHandler(Handler<Throwable> handler)Set an exception handler on the read stream.ClientWebSocketfetch(long amount)Fetch the specifiedamountof elements.ClientWebSocketframeHandler(Handler<WebSocketFrame> handler)Set a frame handler on the connection.ClientWebSockethandler(Handler<Buffer> handler)Set a data handler.ClientWebSocketpause()Pause theReadStream, it sets the buffer infetchmode and clears the actual demand.ClientWebSocketpongHandler(Handler<Buffer> handler)Set a pong frame handler on the connection.default ClientWebSocketresume()Resume reading, and sets the buffer inflowingmode.ClientWebSocketsetWriteQueueMaxSize(int maxSize)Set the maximum size of the write queue tomaxSize.ClientWebSockettextMessageHandler(Handler<String> handler)Set a text message handler on the connection.- 
Methods inherited from interface io.vertx.core.streams.ReadStreamblockingStream, collect, pipe, pipeTo
 - 
Methods inherited from interface io.vertx.core.http.WebSocketshutdownHandler
 - 
Methods inherited from interface io.vertx.core.http.WebSocketBasebinaryHandlerID, 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.WriteStreamend, write, writeQueueFull
 
- 
 
- 
- 
- 
Method Detail- 
connectFuture<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
 
 - 
connectdefault Future<WebSocket> connect(int port, String host, String requestURI) Connect this WebSocket to the specified port, host and relative request URI.- Parameters:
- port- the port
- host- the host
- requestURI- the relative URI
- Returns:
- a future notified when the WebSocket when connected
 
 - 
connectdefault Future<WebSocket> connect(String host, String requestURI) Connect this WebSocket to the host and relative request URI and default port.- Parameters:
- host- the host
- requestURI- the relative URI
- Returns:
- a future notified when the WebSocket when connected
 
 - 
connectdefault 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
 
 - 
pauseClientWebSocket pause() Description copied from interface:ReadStreamPause theReadStream, it sets the buffer infetchmode and clears the actual demand.While it's paused, no data will be sent to the data handler.- Specified by:
- pausein interface- ReadStream<Buffer>
- Specified by:
- pausein interface- WebSocket
- Specified by:
- pausein interface- WebSocketBase
- Returns:
- a reference to this, so the API can be used fluently
 
 - 
resumedefault ClientWebSocket resume() Description copied from interface:ReadStreamResume reading, and sets the buffer inflowingmode. If theReadStreamhas been paused, reading will recommence on it.- Specified by:
- resumein interface- ReadStream<Buffer>
- Specified by:
- resumein interface- WebSocket
- Specified by:
- resumein interface- WebSocketBase
- Returns:
- a reference to this, so the API can be used fluently
 
 - 
fetchClientWebSocket fetch(long amount) Description copied from interface:ReadStreamFetch the specifiedamountof elements. If theReadStreamhas been paused, reading will recommence with the specifiedamountof items, otherwise the specifiedamountwill be added to the current stream demand.- Specified by:
- fetchin interface- ReadStream<Buffer>
- Specified by:
- fetchin interface- WebSocket
- Specified by:
- fetchin interface- WebSocketBase
- Returns:
- a reference to this, so the API can be used fluently
 
 - 
setWriteQueueMaxSizeClientWebSocket setWriteQueueMaxSize(int maxSize) Description copied from interface:WriteStreamSet the maximum size of the write queue tomaxSize. You will still be able to write to the stream even if there is more thanmaxSizeitems in the write queue. This is used as an indicator by classes such asPipeto provide flow control. The value is defined by the implementation of the stream, e.g in bytes for aNetSocket, etc...- Specified by:
- setWriteQueueMaxSizein interface- WebSocket
- Specified by:
- setWriteQueueMaxSizein interface- WebSocketBase
- Specified by:
- setWriteQueueMaxSizein interface- WriteStream<Buffer>
- Parameters:
- maxSize- the max size of the write stream
- Returns:
- a reference to this, so the API can be used fluently
 
 - 
handlerClientWebSocket handler(Handler<Buffer> handler) Description copied from interface:ReadStreamSet a data handler. As data is read, the handler will be called with the data.- Specified by:
- handlerin interface- ReadStream<Buffer>
- Specified by:
- handlerin interface- WebSocket
- Specified by:
- handlerin interface- WebSocketBase
- Returns:
- a reference to this, so the API can be used fluently
 
 - 
endHandlerClientWebSocket endHandler(Handler<Void> endHandler) Description copied from interface:ReadStreamSet an end handler. Once the stream has ended, and there is no more data to be read, this handler will be called.- Specified by:
- endHandlerin interface- ReadStream<Buffer>
- Specified by:
- endHandlerin interface- WebSocket
- Specified by:
- endHandlerin interface- WebSocketBase
- Returns:
- a reference to this, so the API can be used fluently
 
 - 
drainHandlerClientWebSocket drainHandler(Handler<Void> handler) Description copied from interface:WriteStreamSet 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. SeePipefor 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:
- drainHandlerin interface- WebSocket
- Specified by:
- drainHandlerin interface- WebSocketBase
- Specified by:
- drainHandlerin interface- WriteStream<Buffer>
- Parameters:
- handler- the handler
- Returns:
- a reference to this, so the API can be used fluently
 
 - 
closeHandlerClientWebSocket closeHandler(Handler<Void> handler) Description copied from interface:WebSocketBaseSet 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:
- closeHandlerin interface- WebSocket
- Specified by:
- closeHandlerin interface- WebSocketBase
- Parameters:
- handler- the handler
- Returns:
- a reference to this, so the API can be used fluently
 
 - 
frameHandlerClientWebSocket frameHandler(Handler<WebSocketFrame> handler) Description copied from interface:WebSocketBaseSet a frame handler on the connection. This handler will be called when frames are read on the connection.- Specified by:
- frameHandlerin interface- WebSocket
- Specified by:
- frameHandlerin interface- WebSocketBase
- Parameters:
- handler- the handler
- Returns:
- a reference to this, so the API can be used fluently
 
 - 
textMessageHandlerClientWebSocket textMessageHandler(Handler<String> handler) Description copied from interface:WebSocketBaseSet 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:
- textMessageHandlerin interface- WebSocket
- Specified by:
- textMessageHandlerin interface- WebSocketBase
- Parameters:
- handler- the handler
- Returns:
- a reference to this, so the API can be used fluently
 
 - 
binaryMessageHandlerClientWebSocket binaryMessageHandler(Handler<Buffer> handler) Description copied from interface:WebSocketBaseSet 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:
- binaryMessageHandlerin interface- WebSocket
- Specified by:
- binaryMessageHandlerin interface- WebSocketBase
- Parameters:
- handler- the handler
- Returns:
- a reference to this, so the API can be used fluently
 
 - 
pongHandlerClientWebSocket pongHandler(Handler<Buffer> handler) Description copied from interface:WebSocketBaseSet 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:
- pongHandlerin interface- WebSocket
- Specified by:
- pongHandlerin interface- WebSocketBase
- Parameters:
- handler- the handler
- Returns:
- a reference to this, so the API can be used fluently
 
 - 
exceptionHandlerClientWebSocket exceptionHandler(Handler<Throwable> handler) Description copied from interface:ReadStreamSet an exception handler on the read stream.- Specified by:
- exceptionHandlerin interface- ReadStream<Buffer>
- Specified by:
- exceptionHandlerin interface- StreamBase
- Specified by:
- exceptionHandlerin interface- WebSocket
- Specified by:
- exceptionHandlerin interface- WebSocketBase
- Specified by:
- exceptionHandlerin interface- WriteStream<Buffer>
- Parameters:
- handler- the exception handler
- Returns:
- a reference to this, so the API can be used fluently
 
 
- 
 
-