Class ClientWebSocket
- All Implemented Interfaces:
MutinyDelegate,WebSocketBase,ReadStream<Buffer>,StreamBase,WriteStream<Buffer>
original non Mutiny-ified interface using Vert.x codegen.-
Field Summary
Fields -
Constructor Summary
ConstructorsConstructorDescriptionClientWebSocket(io.vertx.core.http.ClientWebSocket delegate) ClientWebSocket(Object delegate) -
Method Summary
Modifier and TypeMethodDescriptionbinaryMessageHandler(Consumer<Buffer> handler) io.smallrye.mutiny.Uni<Void>close()Same asWebSocketBase.close()but with anhandlercalled when the operation completesio.smallrye.mutiny.Uni<Void>close(short statusCode) Same asWebSocketBase.close()but with anhandlercalled when the operation completesio.smallrye.mutiny.Uni<Void>Same asWebSocketBase.close()but with anhandlercalled when the operation completesBlocking variant ofWebSocketBase.close().closeAndAwait(short statusCode) Blocking variant ofWebSocketBase.close(short).closeAndAwait(short statusCode, String reason) Blocking variant ofWebSocketBase.close(short,String).voidVariant ofWebSocketBase.close()that ignores the result of the operation.voidcloseAndForget(short statusCode) Variant ofWebSocketBase.close(short)that ignores the result of the operation.voidcloseAndForget(short statusCode, String reason) Variant ofWebSocketBase.close(short,String)that ignores the result of the operation.closeHandler(Runnable handler) io.smallrye.mutiny.Uni<WebSocket>Connect a WebSocket to the specified port, host and relative request URIio.smallrye.mutiny.Uni<WebSocket>connect(io.vertx.core.http.WebSocketConnectOptions options) Connect a WebSocket with the specified options.io.smallrye.mutiny.Uni<WebSocket>Connect this WebSocket at the relative request URI using the default host and port.io.smallrye.mutiny.Uni<WebSocket>Connect this WebSocket to the host and relative request URI and default port.connectAndAwait(int port, String host, String requestURI) Blocking variant ofconnect(int,String,String).connectAndAwait(io.vertx.core.http.WebSocketConnectOptions options) Blocking variant ofconnect(WebSocketConnectOptions).connectAndAwait(String requestURI) Blocking variant ofconnect(String).connectAndAwait(String host, String requestURI) Blocking variant ofconnect(String,String).voidconnectAndForget(int port, String host, String requestURI) Variant ofconnect(int,String,String)that ignores the result of the operation.voidconnectAndForget(io.vertx.core.http.WebSocketConnectOptions options) Variant ofconnect(WebSocketConnectOptions)that ignores the result of the operation.voidconnectAndForget(String requestURI) Variant ofconnect(String)that ignores the result of the operation.voidconnectAndForget(String host, String requestURI) Variant ofconnect(String,String)that ignores the result of the operation.drainHandler(Runnable handler) io.smallrye.mutiny.Uni<Void>end()CallsWebSocketBase.close()io.smallrye.mutiny.Uni<Void>Same as but with anhandlercalled when the operation completesBlocking variant ofWebSocketBase.end(io.vertx.mutiny.core.buffer.Buffer).endAndAwait(Buffer data) Blocking variant ofio.vertx.mutiny.core.streams.WriteStream#end(io.vertx.mutiny.core.buffer.Buffer).voidVariant ofWebSocketBase.end(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.voidendAndForget(Buffer data) Variant ofio.vertx.mutiny.core.streams.WriteStream#end(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.endHandler(Runnable endHandler) booleanexceptionHandler(Consumer<Throwable> handler) frameHandler(Consumer<WebSocketFrame> handler) io.vertx.core.http.ClientWebSocketinthashCode()headers()booleanisClosed()booleanisSsl()static ClientWebSocketnewInstance(io.vertx.core.http.ClientWebSocket arg) pipe()io.smallrye.mutiny.Uni<Void>pipeTo(WriteStream<Buffer> dst) Pipe thisReadStreamto theWriteStream.pipeToAndAwait(WriteStream<Buffer> dst) Blocking variant ofReadStream.pipeTo(io.vertx.mutiny.core.streams.WriteStream).voidpipeToAndForget(WriteStream<Buffer> dst) Variant ofReadStream.pipeTo(io.vertx.mutiny.core.streams.WriteStream)that ignores the result of the operation.pongHandler(Consumer<Buffer> handler) textMessageHandler(Consumer<String> handler) io.smallrye.mutiny.Multi<Buffer>toMulti()toString()io.smallrye.mutiny.Uni<Void>Same as but with anhandlercalled when the operation completeswriteAndAwait(Buffer data) Blocking variant ofio.vertx.mutiny.core.streams.WriteStream#write(io.vertx.mutiny.core.buffer.Buffer).voidwriteAndForget(Buffer data) Variant ofio.vertx.mutiny.core.streams.WriteStream#write(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.io.smallrye.mutiny.Uni<Void>writeBinaryMessage(Buffer data) Same asWebSocketBase.writeBinaryMessage(io.vertx.mutiny.core.buffer.Buffer)but with anhandlercalled when the operation completesBlocking variant ofWebSocketBase.writeBinaryMessage(io.vertx.mutiny.core.buffer.Buffer).Variant ofWebSocketBase.writeBinaryMessage(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.io.smallrye.mutiny.Uni<Void>writeFinalBinaryFrame(Buffer data) Same asWebSocketBase.writeFinalBinaryFrame(io.vertx.mutiny.core.buffer.Buffer)but with anhandlercalled when the operation completesBlocking variant ofWebSocketBase.writeFinalBinaryFrame(io.vertx.mutiny.core.buffer.Buffer).Variant ofWebSocketBase.writeFinalBinaryFrame(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.io.smallrye.mutiny.Uni<Void>writeFinalTextFrame(String text) Same asWebSocketBase.writeFinalTextFrame(java.lang.String)but with anhandlercalled when the operation completesBlocking variant ofWebSocketBase.writeFinalTextFrame(String).Variant ofWebSocketBase.writeFinalTextFrame(String)that ignores the result of the operation.io.smallrye.mutiny.Uni<Void>writeFrame(WebSocketFrame frame) Same asWebSocketBase.writeFrame(io.vertx.mutiny.core.http.WebSocketFrame)but with anhandlercalled when the operation completeswriteFrameAndAwait(WebSocketFrame frame) Blocking variant ofWebSocketBase.writeFrame(io.vertx.mutiny.core.http.WebSocketFrame).Variant ofWebSocketBase.writeFrame(io.vertx.mutiny.core.http.WebSocketFrame)that ignores the result of the operation.io.smallrye.mutiny.Uni<Void>Writes a ping frame to the connection.writePingAndAwait(Buffer data) Blocking variant ofWebSocketBase.writePing(io.vertx.mutiny.core.buffer.Buffer).writePingAndForget(Buffer data) Variant ofWebSocketBase.writePing(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.io.smallrye.mutiny.Uni<Void>Writes a pong frame to the connection.writePongAndAwait(Buffer data) Blocking variant ofWebSocketBase.writePong(io.vertx.mutiny.core.buffer.Buffer).writePongAndForget(Buffer data) Variant ofWebSocketBase.writePong(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.booleanio.smallrye.mutiny.Uni<Void>writeTextMessage(String text) Same asWebSocketBase.writeTextMessage(java.lang.String)but with anhandlercalled when the operation completesBlocking variant ofWebSocketBase.writeTextMessage(String).Variant ofWebSocketBase.writeTextMessage(String)that ignores the result of the operation.Methods inherited from class io.vertx.mutiny.core.http.WebSocket
fetch, newInstance, pause, resume, setWriteQueueMaxSize
-
Field Details
-
__TYPE_ARG
-
-
Constructor Details
-
ClientWebSocket
public ClientWebSocket(io.vertx.core.http.ClientWebSocket delegate) -
ClientWebSocket
-
-
Method Details
-
getDelegate
public io.vertx.core.http.ClientWebSocket getDelegate()- Specified by:
getDelegatein interfaceMutinyDelegate- Specified by:
getDelegatein interfaceReadStream<Buffer>- Specified by:
getDelegatein interfaceStreamBase- Specified by:
getDelegatein interfaceWebSocketBase- Specified by:
getDelegatein interfaceWriteStream<Buffer>- Overrides:
getDelegatein classWebSocket- Returns:
- the delegate used by this Mutiny object of generated type
-
toString
-
equals
-
hashCode
public int hashCode() -
toSubscriber
- Overrides:
toSubscriberin classWebSocket
-
write
Same as but with anhandlercalled when the operation completesUnlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Specified by:
writein interfaceWebSocketBase- Specified by:
writein interfaceWriteStream<Buffer>- Overrides:
writein classWebSocket- Parameters:
data-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeAndAwait
Blocking variant ofio.vertx.mutiny.core.streams.WriteStream#write(io.vertx.mutiny.core.buffer.Buffer).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Specified by:
writeAndAwaitin interfaceWebSocketBase- Specified by:
writeAndAwaitin interfaceWriteStream<Buffer>- Overrides:
writeAndAwaitin classWebSocket- Parameters:
data-- Returns:
- the Void instance produced by the operation.
-
writeAndForget
Variant ofio.vertx.mutiny.core.streams.WriteStream#write(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.This method subscribes on the result of
io.vertx.mutiny.core.streams.WriteStream#write(io.vertx.mutiny.core.buffer.Buffer), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromio.vertx.mutiny.core.streams.WriteStream#write(io.vertx.mutiny.core.buffer.Buffer)but you don't need to compose it with other operations.- Specified by:
writeAndForgetin interfaceWebSocketBase- Specified by:
writeAndForgetin interfaceWriteStream<Buffer>- Overrides:
writeAndForgetin classWebSocket- Parameters:
data-
-
end
Same as but with anhandlercalled when the operation completesUnlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Specified by:
endin interfaceWebSocketBase- Specified by:
endin interfaceWriteStream<Buffer>- Overrides:
endin classWebSocket- Parameters:
data-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
endAndAwait
Blocking variant ofio.vertx.mutiny.core.streams.WriteStream#end(io.vertx.mutiny.core.buffer.Buffer).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Specified by:
endAndAwaitin interfaceWebSocketBase- Specified by:
endAndAwaitin interfaceWriteStream<Buffer>- Overrides:
endAndAwaitin classWebSocket- Parameters:
data-- Returns:
- the Void instance produced by the operation.
-
endAndForget
Variant ofio.vertx.mutiny.core.streams.WriteStream#end(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.This method subscribes on the result of
io.vertx.mutiny.core.streams.WriteStream#end(io.vertx.mutiny.core.buffer.Buffer), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromio.vertx.mutiny.core.streams.WriteStream#end(io.vertx.mutiny.core.buffer.Buffer)but you don't need to compose it with other operations.- Specified by:
endAndForgetin interfaceWebSocketBase- Specified by:
endAndForgetin interfaceWriteStream<Buffer>- Overrides:
endAndForgetin classWebSocket- Parameters:
data-
-
writeQueueFull
public boolean writeQueueFull()- Specified by:
writeQueueFullin interfaceWebSocketBase- Specified by:
writeQueueFullin interfaceWriteStream<Buffer>- Overrides:
writeQueueFullin classWebSocket- Returns:
trueif write queue is full
-
pipe
- Specified by:
pipein interfaceReadStream<Buffer>- Specified by:
pipein interfaceWebSocketBase- Overrides:
pipein classWebSocket- Returns:
- a pipe
-
pipeTo
Pipe thisReadStreamto theWriteStream.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
handlerwill be called with the result.Unlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Specified by:
pipeToin interfaceReadStream<Buffer>- Specified by:
pipeToin interfaceWebSocketBase- Overrides:
pipeToin classWebSocket- Parameters:
dst- the destination write stream- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
pipeToAndAwait
Blocking variant ofReadStream.pipeTo(io.vertx.mutiny.core.streams.WriteStream).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Specified by:
pipeToAndAwaitin interfaceReadStream<Buffer>- Specified by:
pipeToAndAwaitin interfaceWebSocketBase- Overrides:
pipeToAndAwaitin classWebSocket- Parameters:
dst- the destination write stream- Returns:
- the Void instance produced by the operation.
-
pipeToAndForget
Variant ofReadStream.pipeTo(io.vertx.mutiny.core.streams.WriteStream)that ignores the result of the operation.This method subscribes on the result of
ReadStream.pipeTo(io.vertx.mutiny.core.streams.WriteStream), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromReadStream.pipeTo(io.vertx.mutiny.core.streams.WriteStream)but you don't need to compose it with other operations.- Specified by:
pipeToAndForgetin interfaceReadStream<Buffer>- Specified by:
pipeToAndForgetin interfaceWebSocketBase- Overrides:
pipeToAndForgetin classWebSocket- Parameters:
dst- the destination write stream
-
binaryHandlerID
- Specified by:
binaryHandlerIDin interfaceWebSocketBase- Overrides:
binaryHandlerIDin classWebSocket- Returns:
- the binary handler id
-
textHandlerID
- Specified by:
textHandlerIDin interfaceWebSocketBase- Overrides:
textHandlerIDin classWebSocket- Returns:
- the text handler id
-
subProtocol
- Specified by:
subProtocolin interfaceWebSocketBase- Overrides:
subProtocolin classWebSocket- Returns:
-
closeStatusCode
- Specified by:
closeStatusCodein interfaceWebSocketBase- Overrides:
closeStatusCodein classWebSocket- Returns:
-
closeReason
- Specified by:
closeReasonin interfaceWebSocketBase- Overrides:
closeReasonin classWebSocket- Returns:
-
headers
- Specified by:
headersin interfaceWebSocketBase- Overrides:
headersin classWebSocket- Returns:
- the headers
-
end
CallsWebSocketBase.close()Unlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Specified by:
endin interfaceWebSocketBase- Specified by:
endin interfaceWriteStream<Buffer>- Overrides:
endin classWebSocket- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
endAndAwait
Blocking variant ofWebSocketBase.end(io.vertx.mutiny.core.buffer.Buffer).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Specified by:
endAndAwaitin interfaceWebSocketBase- Specified by:
endAndAwaitin interfaceWriteStream<Buffer>- Overrides:
endAndAwaitin classWebSocket- Returns:
- the Void instance produced by the operation.
-
endAndForget
public void endAndForget()Variant ofWebSocketBase.end(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.This method subscribes on the result of
WebSocketBase.end(io.vertx.mutiny.core.buffer.Buffer), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromWebSocketBase.end(io.vertx.mutiny.core.buffer.Buffer)but you don't need to compose it with other operations.- Specified by:
endAndForgetin interfaceWebSocketBase- Specified by:
endAndForgetin interfaceWriteStream<Buffer>- Overrides:
endAndForgetin classWebSocket
-
close
Same asWebSocketBase.close()but with anhandlercalled when the operation completesUnlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Specified by:
closein interfaceWebSocketBase- Overrides:
closein classWebSocket- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
closeAndAwait
Blocking variant ofWebSocketBase.close().This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Specified by:
closeAndAwaitin interfaceWebSocketBase- Overrides:
closeAndAwaitin classWebSocket- Returns:
- the Void instance produced by the operation.
-
closeAndForget
public void closeAndForget()Variant ofWebSocketBase.close()that ignores the result of the operation.This method subscribes on the result of
WebSocketBase.close(), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromWebSocketBase.close()but you don't need to compose it with other operations.- Specified by:
closeAndForgetin interfaceWebSocketBase- Overrides:
closeAndForgetin classWebSocket
-
close
Same asWebSocketBase.close()but with anhandlercalled when the operation completesUnlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Specified by:
closein interfaceWebSocketBase- Overrides:
closein classWebSocket- Parameters:
statusCode-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
closeAndAwait
Blocking variant ofWebSocketBase.close(short).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Specified by:
closeAndAwaitin interfaceWebSocketBase- Overrides:
closeAndAwaitin classWebSocket- Parameters:
statusCode-- Returns:
- the Void instance produced by the operation.
-
closeAndForget
public void closeAndForget(short statusCode) Variant ofWebSocketBase.close(short)that ignores the result of the operation.This method subscribes on the result of
WebSocketBase.close(short), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromWebSocketBase.close(short)but you don't need to compose it with other operations.- Specified by:
closeAndForgetin interfaceWebSocketBase- Overrides:
closeAndForgetin classWebSocket- Parameters:
statusCode-
-
close
Same asWebSocketBase.close()but with anhandlercalled when the operation completesUnlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Specified by:
closein interfaceWebSocketBase- Overrides:
closein classWebSocket- Parameters:
statusCode-reason-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
closeAndAwait
Blocking variant ofWebSocketBase.close(short,String).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Specified by:
closeAndAwaitin interfaceWebSocketBase- Overrides:
closeAndAwaitin classWebSocket- Parameters:
statusCode-reason-- Returns:
- the Void instance produced by the operation.
-
closeAndForget
Variant ofWebSocketBase.close(short,String)that ignores the result of the operation.This method subscribes on the result of
WebSocketBase.close(short,String), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromWebSocketBase.close(short,String)but you don't need to compose it with other operations.- Specified by:
closeAndForgetin interfaceWebSocketBase- Overrides:
closeAndForgetin classWebSocket- Parameters:
statusCode-reason-
-
remoteAddress
- Specified by:
remoteAddressin interfaceWebSocketBase- Overrides:
remoteAddressin classWebSocket- Returns:
- the remote address for this connection, possibly
null(e.g a server bound on a domain socket). IfuseProxyProtocolis set totrue, the address returned will be of the actual connecting client.
-
localAddress
- Specified by:
localAddressin interfaceWebSocketBase- Overrides:
localAddressin classWebSocket- Returns:
- the local address for this connection, possibly
null(e.g a server bound on a domain socket) IfuseProxyProtocolis set totrue, the address returned will be of the proxy.
-
isSsl
public boolean isSsl()- Specified by:
isSslin interfaceWebSocketBase- Overrides:
isSslin classWebSocket- Returns:
- true if this
HttpConnectionis encrypted via SSL/TLS.
-
isClosed
public boolean isClosed()- Specified by:
isClosedin interfaceWebSocketBase- Overrides:
isClosedin classWebSocket- Returns:
trueif the WebSocket is closed
-
connect
@CheckReturnValue public io.smallrye.mutiny.Uni<WebSocket> connect(int port, String host, String requestURI) Connect a WebSocket to the specified port, host and relative request URIUnlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Parameters:
port- the porthost- the hostrequestURI- the relative URI- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
connectAndAwait
Blocking variant ofconnect(int,String,String).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Parameters:
port- the porthost- the hostrequestURI- the relative URI- Returns:
- the WebSocket instance produced by the operation.
-
connectAndForget
Variant ofconnect(int,String,String)that ignores the result of the operation.This method subscribes on the result of
connect(int,String,String), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromconnect(int,String,String)but you don't need to compose it with other operations.- Parameters:
port- the porthost- the hostrequestURI- the relative URI
-
connect
@CheckReturnValue public io.smallrye.mutiny.Uni<WebSocket> connect(io.vertx.core.http.WebSocketConnectOptions options) Connect a WebSocket with the specified options.Unlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Parameters:
options- the request options- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
connectAndAwait
Blocking variant ofconnect(WebSocketConnectOptions).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Parameters:
options- the request options- Returns:
- the WebSocket instance produced by the operation.
-
connectAndForget
public void connectAndForget(io.vertx.core.http.WebSocketConnectOptions options) Variant ofconnect(WebSocketConnectOptions)that ignores the result of the operation.This method subscribes on the result of
connect(WebSocketConnectOptions), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromconnect(WebSocketConnectOptions)but you don't need to compose it with other operations.- Parameters:
options- the request options
-
connect
Connect this WebSocket to the host and relative request URI and default port.Unlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Parameters:
host- the hostrequestURI- the relative URI- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
connectAndAwait
Blocking variant ofconnect(String,String).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Parameters:
host- the hostrequestURI- the relative URI- Returns:
- the WebSocket instance produced by the operation.
-
connectAndForget
Variant ofconnect(String,String)that ignores the result of the operation.This method subscribes on the result of
connect(String,String), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromconnect(String,String)but you don't need to compose it with other operations.- Parameters:
host- the hostrequestURI- the relative URI
-
connect
Connect this WebSocket at the relative request URI using the default host and port.Unlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Parameters:
requestURI- the relative URI- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
connectAndAwait
Blocking variant ofconnect(String).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Parameters:
requestURI- the relative URI- Returns:
- the WebSocket instance produced by the operation.
-
connectAndForget
Variant ofconnect(String)that ignores the result of the operation.This method subscribes on the result of
connect(String), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromconnect(String)but you don't need to compose it with other operations.- Parameters:
requestURI- the relative URI
-
handler
- Specified by:
handlerin interfaceReadStream<Buffer>- Specified by:
handlerin interfaceWebSocketBase- Overrides:
handlerin classWebSocket- Returns:
-
endHandler
- Specified by:
endHandlerin interfaceReadStream<Buffer>- Specified by:
endHandlerin interfaceWebSocketBase- Overrides:
endHandlerin classWebSocket- Returns:
-
drainHandler
- Specified by:
drainHandlerin interfaceWebSocketBase- Specified by:
drainHandlerin interfaceWriteStream<Buffer>- Overrides:
drainHandlerin classWebSocket- Parameters:
handler- the handler- Returns:
-
closeHandler
- Specified by:
closeHandlerin interfaceWebSocketBase- Overrides:
closeHandlerin classWebSocket- Parameters:
handler- the handler- Returns:
-
frameHandler
- Specified by:
frameHandlerin interfaceWebSocketBase- Overrides:
frameHandlerin classWebSocket- Parameters:
handler- the handler- Returns:
-
textMessageHandler
- Specified by:
textMessageHandlerin interfaceWebSocketBase- Overrides:
textMessageHandlerin classWebSocket- Parameters:
handler- the handler- Returns:
-
binaryMessageHandler
- Specified by:
binaryMessageHandlerin interfaceWebSocketBase- Overrides:
binaryMessageHandlerin classWebSocket- Parameters:
handler- the handler- Returns:
-
pongHandler
- Specified by:
pongHandlerin interfaceWebSocketBase- Overrides:
pongHandlerin classWebSocket- Parameters:
handler- the handler- Returns:
-
exceptionHandler
- Specified by:
exceptionHandlerin interfaceReadStream<Buffer>- Specified by:
exceptionHandlerin interfaceStreamBase- Specified by:
exceptionHandlerin interfaceWebSocketBase- Specified by:
exceptionHandlerin interfaceWriteStream<Buffer>- Overrides:
exceptionHandlerin classWebSocket- Parameters:
handler- the exception handler- Returns:
-
writeFrame
Description copied from interface:WebSocketBaseSame asWebSocketBase.writeFrame(io.vertx.mutiny.core.http.WebSocketFrame)but with anhandlercalled when the operation completesUnlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Specified by:
writeFramein interfaceWebSocketBase- Overrides:
writeFramein classWebSocket- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeFrameAndAwait
Description copied from interface:WebSocketBaseBlocking variant ofWebSocketBase.writeFrame(io.vertx.mutiny.core.http.WebSocketFrame).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Specified by:
writeFrameAndAwaitin interfaceWebSocketBase- Overrides:
writeFrameAndAwaitin classWebSocket- Returns:
- the Void instance produced by the operation.
-
writeFrameAndForget
Description copied from interface:WebSocketBaseVariant ofWebSocketBase.writeFrame(io.vertx.mutiny.core.http.WebSocketFrame)that ignores the result of the operation.This method subscribes on the result of
WebSocketBase.writeFrame(io.vertx.mutiny.core.http.WebSocketFrame), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromWebSocketBase.writeFrame(io.vertx.mutiny.core.http.WebSocketFrame)but you don't need to compose it with other operations.- Specified by:
writeFrameAndForgetin interfaceWebSocketBase- Overrides:
writeFrameAndForgetin classWebSocket- Returns:
- the instance of WebSocketBase to chain method calls.
-
writeFinalTextFrame
Description copied from interface:WebSocketBaseSame asWebSocketBase.writeFinalTextFrame(java.lang.String)but with anhandlercalled when the operation completesUnlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Specified by:
writeFinalTextFramein interfaceWebSocketBase- Overrides:
writeFinalTextFramein classWebSocket- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeFinalTextFrameAndAwait
Description copied from interface:WebSocketBaseBlocking variant ofWebSocketBase.writeFinalTextFrame(String).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Specified by:
writeFinalTextFrameAndAwaitin interfaceWebSocketBase- Overrides:
writeFinalTextFrameAndAwaitin classWebSocket- Returns:
- the Void instance produced by the operation.
-
writeFinalTextFrameAndForget
Description copied from interface:WebSocketBaseVariant ofWebSocketBase.writeFinalTextFrame(String)that ignores the result of the operation.This method subscribes on the result of
WebSocketBase.writeFinalTextFrame(String), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromWebSocketBase.writeFinalTextFrame(String)but you don't need to compose it with other operations.- Specified by:
writeFinalTextFrameAndForgetin interfaceWebSocketBase- Overrides:
writeFinalTextFrameAndForgetin classWebSocket- Returns:
- the instance of WebSocketBase to chain method calls.
-
writeFinalBinaryFrame
Description copied from interface:WebSocketBaseSame asWebSocketBase.writeFinalBinaryFrame(io.vertx.mutiny.core.buffer.Buffer)but with anhandlercalled when the operation completesUnlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Specified by:
writeFinalBinaryFramein interfaceWebSocketBase- Overrides:
writeFinalBinaryFramein classWebSocket- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeFinalBinaryFrameAndAwait
Description copied from interface:WebSocketBaseBlocking variant ofWebSocketBase.writeFinalBinaryFrame(io.vertx.mutiny.core.buffer.Buffer).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Specified by:
writeFinalBinaryFrameAndAwaitin interfaceWebSocketBase- Overrides:
writeFinalBinaryFrameAndAwaitin classWebSocket- Returns:
- the Void instance produced by the operation.
-
writeFinalBinaryFrameAndForget
Description copied from interface:WebSocketBaseVariant ofWebSocketBase.writeFinalBinaryFrame(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.This method subscribes on the result of
WebSocketBase.writeFinalBinaryFrame(io.vertx.mutiny.core.buffer.Buffer), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromWebSocketBase.writeFinalBinaryFrame(io.vertx.mutiny.core.buffer.Buffer)but you don't need to compose it with other operations.- Specified by:
writeFinalBinaryFrameAndForgetin interfaceWebSocketBase- Overrides:
writeFinalBinaryFrameAndForgetin classWebSocket- Returns:
- the instance of WebSocketBase to chain method calls.
-
writeBinaryMessage
Description copied from interface:WebSocketBaseSame asWebSocketBase.writeBinaryMessage(io.vertx.mutiny.core.buffer.Buffer)but with anhandlercalled when the operation completesUnlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Specified by:
writeBinaryMessagein interfaceWebSocketBase- Overrides:
writeBinaryMessagein classWebSocket- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeBinaryMessageAndAwait
Description copied from interface:WebSocketBaseBlocking variant ofWebSocketBase.writeBinaryMessage(io.vertx.mutiny.core.buffer.Buffer).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Specified by:
writeBinaryMessageAndAwaitin interfaceWebSocketBase- Overrides:
writeBinaryMessageAndAwaitin classWebSocket- Returns:
- the Void instance produced by the operation.
-
writeBinaryMessageAndForget
Description copied from interface:WebSocketBaseVariant ofWebSocketBase.writeBinaryMessage(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.This method subscribes on the result of
WebSocketBase.writeBinaryMessage(io.vertx.mutiny.core.buffer.Buffer), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromWebSocketBase.writeBinaryMessage(io.vertx.mutiny.core.buffer.Buffer)but you don't need to compose it with other operations.- Specified by:
writeBinaryMessageAndForgetin interfaceWebSocketBase- Overrides:
writeBinaryMessageAndForgetin classWebSocket- Returns:
- the instance of WebSocketBase to chain method calls.
-
writeTextMessage
Description copied from interface:WebSocketBaseSame asWebSocketBase.writeTextMessage(java.lang.String)but with anhandlercalled when the operation completesUnlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Specified by:
writeTextMessagein interfaceWebSocketBase- Overrides:
writeTextMessagein classWebSocket- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeTextMessageAndAwait
Description copied from interface:WebSocketBaseBlocking variant ofWebSocketBase.writeTextMessage(String).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Specified by:
writeTextMessageAndAwaitin interfaceWebSocketBase- Overrides:
writeTextMessageAndAwaitin classWebSocket- Returns:
- the Void instance produced by the operation.
-
writeTextMessageAndForget
Description copied from interface:WebSocketBaseVariant ofWebSocketBase.writeTextMessage(String)that ignores the result of the operation.This method subscribes on the result of
WebSocketBase.writeTextMessage(String), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromWebSocketBase.writeTextMessage(String)but you don't need to compose it with other operations.- Specified by:
writeTextMessageAndForgetin interfaceWebSocketBase- Overrides:
writeTextMessageAndForgetin classWebSocket- Returns:
- the instance of WebSocketBase to chain method calls.
-
writePing
Description copied from interface:WebSocketBaseWrites a ping frame to the connection. This will be written in a single frame. Ping frames may be at most 125 bytes (octets).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.
Unlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Specified by:
writePingin interfaceWebSocketBase- Overrides:
writePingin classWebSocket- Parameters:
data- the data to write, may be at most 125 bytes- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writePingAndAwait
Description copied from interface:WebSocketBaseBlocking variant ofWebSocketBase.writePing(io.vertx.mutiny.core.buffer.Buffer).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Specified by:
writePingAndAwaitin interfaceWebSocketBase- Overrides:
writePingAndAwaitin classWebSocket- Parameters:
data- the data to write, may be at most 125 bytes- Returns:
- the Void instance produced by the operation.
-
writePingAndForget
Description copied from interface:WebSocketBaseVariant ofWebSocketBase.writePing(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.This method subscribes on the result of
WebSocketBase.writePing(io.vertx.mutiny.core.buffer.Buffer), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromWebSocketBase.writePing(io.vertx.mutiny.core.buffer.Buffer)but you don't need to compose it with other operations.- Specified by:
writePingAndForgetin interfaceWebSocketBase- Overrides:
writePingAndForgetin classWebSocket- Parameters:
data- the data to write, may be at most 125 bytes- Returns:
- the instance of WebSocketBase to chain method calls.
-
writePong
Description copied from interface:WebSocketBaseWrites a pong frame to the connection. This will be written in a single frame. Pong frames may be at most 125 bytes (octets).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.
Unlike the bare Vert.x variant, this method returns a
Uni. Don't forget to subscribe on it to trigger the operation.- Specified by:
writePongin interfaceWebSocketBase- Overrides:
writePongin classWebSocket- Parameters:
data- the data to write, may be at most 125 bytes- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writePongAndAwait
Description copied from interface:WebSocketBaseBlocking variant ofWebSocketBase.writePong(io.vertx.mutiny.core.buffer.Buffer).This method waits for the completion of the underlying asynchronous operation. If the operation completes successfully, the result is returned, otherwise the failure is thrown (potentially wrapped in a RuntimeException).
- Specified by:
writePongAndAwaitin interfaceWebSocketBase- Overrides:
writePongAndAwaitin classWebSocket- Parameters:
data- the data to write, may be at most 125 bytes- Returns:
- the Void instance produced by the operation.
-
writePongAndForget
Description copied from interface:WebSocketBaseVariant ofWebSocketBase.writePong(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.This method subscribes on the result of
WebSocketBase.writePong(io.vertx.mutiny.core.buffer.Buffer), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromWebSocketBase.writePong(io.vertx.mutiny.core.buffer.Buffer)but you don't need to compose it with other operations.- Specified by:
writePongAndForgetin interfaceWebSocketBase- Overrides:
writePongAndForgetin classWebSocket- Parameters:
data- the data to write, may be at most 125 bytes- Returns:
- the instance of WebSocketBase to chain method calls.
-
sslSession
- Specified by:
sslSessionin interfaceWebSocketBase- Overrides:
sslSessionin classWebSocket- Returns:
- SSLSession associated with the underlying socket. Returns null if connection is not SSL.
-
toMulti
- Specified by:
toMultiin interfaceReadStream<Buffer>- Overrides:
toMultiin classWebSocket
-
toBlockingIterable
- Overrides:
toBlockingIterablein classWebSocket
-
toBlockingStream
- Overrides:
toBlockingStreamin classWebSocket
-
newInstance
-