public class WebSocket extends Object implements WebSocketBase
original
non RX-ified interface using Vert.x codegen.Modifier and Type | Field and Description |
---|---|
static io.vertx.lang.rx.TypeArg<WebSocket> |
__TYPE_ARG |
Constructor and Description |
---|
WebSocket(Object delegate) |
WebSocket(WebSocket delegate) |
clone, finalize, getClass, notify, notifyAll, wait, wait, wait
newInstance
newInstance, newInstance
newInstance, newInstance
newInstance
public static final io.vertx.lang.rx.TypeArg<WebSocket> __TYPE_ARG
public WebSocket(WebSocket delegate)
public WebSocket(Object delegate)
public WebSocket getDelegate()
getDelegate
in interface WebSocketBase
getDelegate
in interface ReadStream<Buffer>
getDelegate
in interface StreamBase
getDelegate
in interface WriteStream<Buffer>
public Observable<Buffer> toObservable()
toObservable
in interface ReadStream<Buffer>
public WriteStreamSubscriber<Buffer> toSubscriber()
toSubscriber
in interface WriteStream<Buffer>
public Pipe<Buffer> pipe()
WriteStream
.pipe
in interface WebSocketBase
pipe
in interface ReadStream<Buffer>
public void pipeTo(WriteStream<Buffer> dst, Handler<AsyncResult<Void>> handler)
ReadStream
to the WriteStream
.
Elements emitted by this stream will be written to the write stream until this stream ends or fails.
Once this stream has ended or failed, the write stream will be ended and the handler
will be
called with the result.
pipeTo
in interface WebSocketBase
pipeTo
in interface ReadStream<Buffer>
dst
- the destination write streamhandler
- public void pipeTo(WriteStream<Buffer> dst)
ReadStream
to the WriteStream
.
Elements emitted by this stream will be written to the write stream until this stream ends or fails.
Once this stream has ended or failed, the write stream will be ended and the handler
will be
called with the result.
pipeTo
in interface WebSocketBase
pipeTo
in interface ReadStream<Buffer>
dst
- the destination write streampublic Single<Void> rxPipeTo(WriteStream<Buffer> dst)
ReadStream
to the WriteStream
.
Elements emitted by this stream will be written to the write stream until this stream ends or fails.
Once this stream has ended or failed, the write stream will be ended and the handler
will be
called with the result.
rxPipeTo
in interface WebSocketBase
rxPipeTo
in interface ReadStream<Buffer>
dst
- the destination write streampublic void write(Buffer data, Handler<AsyncResult<Void>> handler)
handler
called when the operation completeswrite
in interface WebSocketBase
write
in interface WriteStream<Buffer>
data
- handler
- public void write(Buffer data)
handler
called when the operation completeswrite
in interface WebSocketBase
write
in interface WriteStream<Buffer>
data
- public Single<Void> rxWrite(Buffer data)
handler
called when the operation completesrxWrite
in interface WebSocketBase
rxWrite
in interface WriteStream<Buffer>
data
- public void end(Buffer data, Handler<AsyncResult<Void>> handler)
handler
called when the operation completesend
in interface WebSocketBase
end
in interface WriteStream<Buffer>
data
- handler
- public void end(Buffer data)
handler
called when the operation completesend
in interface WebSocketBase
end
in interface WriteStream<Buffer>
data
- public Single<Void> rxEnd(Buffer data)
handler
called when the operation completesrxEnd
in interface WebSocketBase
rxEnd
in interface WriteStream<Buffer>
data
- public boolean writeQueueFull()
true
if there are more bytes in the write queue than the value set using setWriteQueueMaxSize(int)
writeQueueFull
in interface WebSocketBase
writeQueueFull
in interface WriteStream<Buffer>
true
if write queue is fullpublic String binaryHandlerID()
WebSocket
is created, it may register an event handler with the event bus - the ID of that
handler is given by this method.
By default, no handler is registered, the feature must be enabled via WebSocketConnectOptions
or HttpServerOptions
.
Given this ID, a different event loop can send a binary frame to that event handler using the event bus and that buffer will be received by this instance in its own event loop and written to the underlying connection. This allows you to write data to other WebSockets which are owned by different event loops.
binaryHandlerID
in interface WebSocketBase
public String textHandlerID()
WebSocket
is created, it may register an event handler with the eventbus, the ID of that
handler is given by textHandlerID
.
By default, no handler is registered, the feature must be enabled via WebSocketConnectOptions
or HttpServerOptions
.
Given this ID, a different event loop can send a text frame to that event handler using the event bus and that buffer will be received by this instance in its own event loop and written to the underlying connection. This allows you to write data to other WebSockets which are owned by different event loops.
textHandlerID
in interface WebSocketBase
public String subProtocol()
null
when the handler receives the WebSocket callback as the
handshake will not be completed yet.subProtocol
in interface WebSocketBase
public Short closeStatusCode()
null
when not yet received.closeStatusCode
in interface WebSocketBase
public String closeReason()
null
when not yet received.closeReason
in interface WebSocketBase
public MultiMap headers()
null
on subsequent interactions.headers
in interface WebSocketBase
public WebSocketBase textMessageHandler(Handler<String> handler)
WebSocketBase.binaryMessageHandler(io.vertx.core.Handler<io.vertx.rxjava.core.buffer.Buffer>)
, but the buffer will be converted to a String firsttextMessageHandler
in interface WebSocketBase
handler
- the handlerpublic WebSocketBase binaryMessageHandler(Handler<Buffer> handler)
handler(io.vertx.core.Handler<io.vertx.rxjava.core.buffer.Buffer>)
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 (using WebSocketFrame.isFinal()
to find the boundaries).binaryMessageHandler
in interface WebSocketBase
handler
- the handlerpublic WebSocketBase pongHandler(Handler<Buffer> handler)
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.
pongHandler
in interface WebSocketBase
handler
- the handlerpublic void end(Handler<AsyncResult<Void>> handler)
end
in interface WebSocketBase
end
in interface WriteStream<Buffer>
handler
- public void end()
end
in interface WebSocketBase
end
in interface WriteStream<Buffer>
public Single<Void> rxEnd()
rxEnd
in interface WebSocketBase
rxEnd
in interface WriteStream<Buffer>
public void close(Handler<AsyncResult<Void>> handler)
WebSocketBase.close(io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completesclose
in interface WebSocketBase
handler
- public void close()
WebSocketBase.close(io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completesclose
in interface WebSocketBase
public Single<Void> rxClose()
WebSocketBase.close(io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completesrxClose
in interface WebSocketBase
public void close(short statusCode, Handler<AsyncResult<Void>> handler)
WebSocketBase.close(io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completesclose
in interface WebSocketBase
statusCode
- handler
- public void close(short statusCode)
WebSocketBase.close(io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completesclose
in interface WebSocketBase
statusCode
- public Single<Void> rxClose(short statusCode)
WebSocketBase.close(io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completesrxClose
in interface WebSocketBase
statusCode
- public void close(short statusCode, String reason, Handler<AsyncResult<Void>> handler)
WebSocketBase.close(io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completesclose
in interface WebSocketBase
statusCode
- reason
- handler
- public void close(short statusCode, String reason)
WebSocketBase.close(io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completesclose
in interface WebSocketBase
statusCode
- reason
- public Single<Void> rxClose(short statusCode, String reason)
WebSocketBase.close(io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completesrxClose
in interface WebSocketBase
statusCode
- reason
- public SocketAddress remoteAddress()
remoteAddress
in interface WebSocketBase
null
(e.g a server bound on a domain socket). If useProxyProtocol
is set to true
, the address returned will be of the actual connecting client.public SocketAddress localAddress()
localAddress
in interface WebSocketBase
null
(e.g a server bound on a domain socket) If useProxyProtocol
is set to true
, the address returned will be of the proxy.public boolean isSsl()
isSsl
in interface WebSocketBase
HttpConnection
is encrypted via SSL/TLS.public boolean isClosed()
isClosed
in interface WebSocketBase
true
if the WebSocket is closedpublic WebSocket exceptionHandler(Handler<Throwable> handler)
ReadStream
exceptionHandler
in interface WebSocketBase
exceptionHandler
in interface ReadStream<Buffer>
exceptionHandler
in interface StreamBase
exceptionHandler
in interface WriteStream<Buffer>
handler
- the exception handlerpublic WebSocket handler(Handler<Buffer> handler)
ReadStream
handler
in interface WebSocketBase
handler
in interface ReadStream<Buffer>
public WebSocket pause()
ReadStream
ReadStream
, it sets the buffer in fetch
mode and clears the actual demand.
While it's paused, no data will be sent to the data handler
.
pause
in interface WebSocketBase
pause
in interface ReadStream<Buffer>
public WebSocket resume()
ReadStream
flowing
mode.
If the ReadStream
has been paused, reading will recommence on it.resume
in interface WebSocketBase
resume
in interface ReadStream<Buffer>
public WebSocket fetch(long amount)
ReadStream
amount
of elements. If the ReadStream
has been paused, reading will
recommence with the specified amount
of items, otherwise the specified amount
will
be added to the current stream demand.fetch
in interface WebSocketBase
fetch
in interface ReadStream<Buffer>
public WebSocket endHandler(Handler<Void> endHandler)
ReadStream
endHandler
in interface WebSocketBase
endHandler
in interface ReadStream<Buffer>
public WebSocket setWriteQueueMaxSize(int maxSize)
WriteStream
maxSize
. You will still be able to write to the stream even
if there is more than maxSize
items in the write queue. This is used as an indicator by classes such as
Pipe
to provide flow control.
The value is defined by the implementation of the stream, e.g in bytes for a
NetSocket
, etc...setWriteQueueMaxSize
in interface WebSocketBase
setWriteQueueMaxSize
in interface WriteStream<Buffer>
maxSize
- the max size of the write streampublic WebSocket drainHandler(Handler<Void> handler)
WriteStream
Pipe
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
.
drainHandler
in interface WebSocketBase
drainHandler
in interface WriteStream<Buffer>
handler
- the handlerpublic WebSocket writeFrame(WebSocketFrame frame, Handler<AsyncResult<Void>> handler)
WebSocketBase
WebSocketBase.writeFrame(io.vertx.rxjava.core.http.WebSocketFrame, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completeswriteFrame
in interface WebSocketBase
public WebSocket writeFrame(WebSocketFrame frame)
WebSocketBase
WebSocketBase.writeFrame(io.vertx.rxjava.core.http.WebSocketFrame, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completeswriteFrame
in interface WebSocketBase
public Single<Void> rxWriteFrame(WebSocketFrame frame)
WebSocketBase
WebSocketBase.writeFrame(io.vertx.rxjava.core.http.WebSocketFrame, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completesrxWriteFrame
in interface WebSocketBase
public WebSocket writeFinalTextFrame(String text, Handler<AsyncResult<Void>> handler)
WebSocketBase
WebSocketBase.writeFinalTextFrame(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completeswriteFinalTextFrame
in interface WebSocketBase
public WebSocket writeFinalTextFrame(String text)
WebSocketBase
WebSocketBase.writeFinalTextFrame(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completeswriteFinalTextFrame
in interface WebSocketBase
public Single<Void> rxWriteFinalTextFrame(String text)
WebSocketBase
WebSocketBase.writeFinalTextFrame(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completesrxWriteFinalTextFrame
in interface WebSocketBase
public WebSocket writeFinalBinaryFrame(Buffer data, Handler<AsyncResult<Void>> handler)
WebSocketBase
WebSocketBase.writeFinalBinaryFrame(io.vertx.rxjava.core.buffer.Buffer, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completeswriteFinalBinaryFrame
in interface WebSocketBase
public WebSocket writeFinalBinaryFrame(Buffer data)
WebSocketBase
WebSocketBase.writeFinalBinaryFrame(io.vertx.rxjava.core.buffer.Buffer, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completeswriteFinalBinaryFrame
in interface WebSocketBase
public Single<Void> rxWriteFinalBinaryFrame(Buffer data)
WebSocketBase
WebSocketBase.writeFinalBinaryFrame(io.vertx.rxjava.core.buffer.Buffer, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completesrxWriteFinalBinaryFrame
in interface WebSocketBase
public WebSocket writeBinaryMessage(Buffer data, Handler<AsyncResult<Void>> handler)
WebSocketBase
WebSocketBase.writeBinaryMessage(io.vertx.rxjava.core.buffer.Buffer, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completeswriteBinaryMessage
in interface WebSocketBase
public WebSocket writeBinaryMessage(Buffer data)
WebSocketBase
WebSocketBase.writeBinaryMessage(io.vertx.rxjava.core.buffer.Buffer, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completeswriteBinaryMessage
in interface WebSocketBase
public Single<Void> rxWriteBinaryMessage(Buffer data)
WebSocketBase
WebSocketBase.writeBinaryMessage(io.vertx.rxjava.core.buffer.Buffer, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completesrxWriteBinaryMessage
in interface WebSocketBase
public WebSocket writeTextMessage(String text, Handler<AsyncResult<Void>> handler)
WebSocketBase
WebSocketBase.writeTextMessage(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completeswriteTextMessage
in interface WebSocketBase
public WebSocket writeTextMessage(String text)
WebSocketBase
WebSocketBase.writeTextMessage(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completeswriteTextMessage
in interface WebSocketBase
public Single<Void> rxWriteTextMessage(String text)
WebSocketBase
WebSocketBase.writeTextMessage(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with an handler
called when the operation completesrxWriteTextMessage
in interface WebSocketBase
public WebSocket writePing(Buffer data, Handler<AsyncResult<Void>> handler)
WebSocketBase
This method should not be used to write application data and should only be used for implementing a keep alive or to ensure the client is still responsive, see RFC 6455 Section section 5.5.2.
There is no handler for ping frames because RFC 6455 clearly states that the only response to a ping frame is a pong frame with identical contents.
writePing
in interface WebSocketBase
data
- the data to write, may be at most 125 byteshandler
- called when the ping frame has been successfully writtenpublic WebSocket writePing(Buffer data)
WebSocketBase
This method should not be used to write application data and should only be used for implementing a keep alive or to ensure the client is still responsive, see RFC 6455 Section section 5.5.2.
There is no handler for ping frames because RFC 6455 clearly states that the only response to a ping frame is a pong frame with identical contents.
writePing
in interface WebSocketBase
data
- the data to write, may be at most 125 bytespublic Single<Void> rxWritePing(Buffer data)
WebSocketBase
This method should not be used to write application data and should only be used for implementing a keep alive or to ensure the client is still responsive, see RFC 6455 Section section 5.5.2.
There is no handler for ping frames because RFC 6455 clearly states that the only response to a ping frame is a pong frame with identical contents.
rxWritePing
in interface WebSocketBase
data
- the data to write, may be at most 125 bytespublic WebSocket writePong(Buffer data, Handler<AsyncResult<Void>> handler)
WebSocketBase
This method should not be used to write application data and should only be used for implementing a keep alive or to ensure the client is still responsive, see RFC 6455 section 5.5.2.
There is no need to manually write a pong frame, as the server and client both handle responding to a ping from with a pong from automatically and this is exposed to users. RFC 6455 section 5.5.3 states that pongs may be sent unsolicited in order to implement a one way heartbeat.
writePong
in interface WebSocketBase
data
- the data to write, may be at most 125 byteshandler
- called when the pong frame has been successfully writtenpublic WebSocket writePong(Buffer data)
WebSocketBase
This method should not be used to write application data and should only be used for implementing a keep alive or to ensure the client is still responsive, see RFC 6455 section 5.5.2.
There is no need to manually write a pong frame, as the server and client both handle responding to a ping from with a pong from automatically and this is exposed to users. RFC 6455 section 5.5.3 states that pongs may be sent unsolicited in order to implement a one way heartbeat.
writePong
in interface WebSocketBase
data
- the data to write, may be at most 125 bytespublic Single<Void> rxWritePong(Buffer data)
WebSocketBase
This method should not be used to write application data and should only be used for implementing a keep alive or to ensure the client is still responsive, see RFC 6455 section 5.5.2.
There is no need to manually write a pong frame, as the server and client both handle responding to a ping from with a pong from automatically and this is exposed to users. RFC 6455 section 5.5.3 states that pongs may be sent unsolicited in order to implement a one way heartbeat.
rxWritePong
in interface WebSocketBase
data
- the data to write, may be at most 125 bytespublic WebSocket closeHandler(Handler<Void> handler)
WebSocketBase
WebSocketBase.closeStatusCode()
will return the status code and WebSocketBase.closeReason()
will return the reason.closeHandler
in interface WebSocketBase
handler
- the handlerpublic WebSocket frameHandler(Handler<WebSocketFrame> handler)
WebSocketBase
frameHandler
in interface WebSocketBase
handler
- the handlerpublic SSLSession sslSession()
Copyright © 2024 Eclipse. All rights reserved.