Class WebSocket
- java.lang.Object
-
- io.vertx.mutiny.core.http.WebSocket
-
- All Implemented Interfaces:
WebSocketBase,ReadStream<Buffer>,StreamBase,WriteStream<Buffer>
public class WebSocket extends Object implements WebSocketBase
Represents a client-side WebSocket. NOTE: This class has been automatically generated from theoriginalnon Mutiny-ified interface using Vert.x codegen.
-
-
Field Summary
Fields Modifier and Type Field Description static TypeArg<WebSocket>__TYPE_ARG
-
Method Summary
-
-
-
Constructor Detail
-
WebSocket
public WebSocket(io.vertx.core.http.WebSocket delegate)
-
WebSocket
public WebSocket(Object delegate)
-
-
Method Detail
-
getDelegate
public io.vertx.core.http.WebSocket getDelegate()
- Specified by:
getDelegatein interfaceReadStream<Buffer>- Specified by:
getDelegatein interfaceStreamBase- Specified by:
getDelegatein interfaceWebSocketBase- Specified by:
getDelegatein interfaceWriteStream<Buffer>
-
toSubscriber
@CheckReturnValue public WriteStreamSubscriber<Buffer> toSubscriber()
-
write
@CheckReturnValue public io.smallrye.mutiny.Uni<Void> write(Buffer data)
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>- Parameters:
data-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeAndAwait
public Void writeAndAwait(Buffer data)
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>- Parameters:
data-- Returns:
- the Void instance produced by the operation.
-
writeAndForget
public void writeAndForget(Buffer data)
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>- Parameters:
data-
-
end
@CheckReturnValue public io.smallrye.mutiny.Uni<Void> end(Buffer data)
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>- Parameters:
data-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
endAndAwait
public Void endAndAwait(Buffer data)
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>- Parameters:
data-- Returns:
- the Void instance produced by the operation.
-
endAndForget
public void endAndForget(Buffer data)
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>- Parameters:
data-
-
writeQueueFull
public boolean writeQueueFull()
- Specified by:
writeQueueFullin interfaceWebSocketBase- Specified by:
writeQueueFullin interfaceWriteStream<Buffer>- Returns:
trueif write queue is full
-
pipe
public Pipe<Buffer> pipe()
- Specified by:
pipein interfaceReadStream<Buffer>- Specified by:
pipein interfaceWebSocketBase- Returns:
- a pipe
-
pipeTo
@CheckReturnValue public io.smallrye.mutiny.Uni<Void> pipeTo(WriteStream<Buffer> dst)
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- Parameters:
dst- the destination write stream- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
pipeToAndAwait
public Void pipeToAndAwait(WriteStream<Buffer> dst)
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- Parameters:
dst- the destination write stream- Returns:
- the Void instance produced by the operation.
-
pipeToAndForget
public void pipeToAndForget(WriteStream<Buffer> dst)
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- Parameters:
dst- the destination write stream
-
binaryHandlerID
public String binaryHandlerID()
- Specified by:
binaryHandlerIDin interfaceWebSocketBase- Returns:
- the binary handler id
-
textHandlerID
public String textHandlerID()
- Specified by:
textHandlerIDin interfaceWebSocketBase- Returns:
-
subProtocol
public String subProtocol()
- Specified by:
subProtocolin interfaceWebSocketBase- Returns:
-
closeStatusCode
public Short closeStatusCode()
- Specified by:
closeStatusCodein interfaceWebSocketBase- Returns:
-
closeReason
public String closeReason()
- Specified by:
closeReasonin interfaceWebSocketBase- Returns:
-
headers
public MultiMap headers()
- Specified by:
headersin interfaceWebSocketBase- Returns:
- the headers
-
writePing
@CheckReturnValue public io.smallrye.mutiny.Uni<Void> writePing(Buffer data)
Writes 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- 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
public Void writePingAndAwait(Buffer data)
Blocking 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- Parameters:
data- the data to write, may be at most 125 bytes- Returns:
- the Void instance produced by the operation.
-
writePingAndForget
public WebSocketBase writePingAndForget(Buffer data)
Variant 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- Parameters:
data- the data to write, may be at most 125 bytes- Returns:
- the instance of WebSocketBase to chain method calls.
-
writePong
@CheckReturnValue public io.smallrye.mutiny.Uni<Void> writePong(Buffer data)
Writes 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- 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
public Void writePongAndAwait(Buffer data)
Blocking 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- Parameters:
data- the data to write, may be at most 125 bytes- Returns:
- the Void instance produced by the operation.
-
writePongAndForget
public WebSocketBase writePongAndForget(Buffer data)
Variant 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- Parameters:
data- the data to write, may be at most 125 bytes- Returns:
- the instance of WebSocketBase to chain method calls.
-
textMessageHandler
public WebSocketBase textMessageHandler(Consumer<String> handler)
- Specified by:
textMessageHandlerin interfaceWebSocketBase- Parameters:
handler- the handler- Returns:
-
binaryMessageHandler
public WebSocketBase binaryMessageHandler(Consumer<Buffer> handler)
- Specified by:
binaryMessageHandlerin interfaceWebSocketBase- Parameters:
handler- the handler- Returns:
-
pongHandler
public WebSocketBase pongHandler(Consumer<Buffer> handler)
- Specified by:
pongHandlerin interfaceWebSocketBase- Parameters:
handler- the handler- Returns:
-
end
@CheckReturnValue public io.smallrye.mutiny.Uni<Void> 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>- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
endAndAwait
public Void 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>- 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>
-
close
@CheckReturnValue public io.smallrye.mutiny.Uni<Void> 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- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
closeAndAwait
public Void 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- 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
-
close
@CheckReturnValue public io.smallrye.mutiny.Uni<Void> close(short statusCode)
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- Parameters:
statusCode-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
closeAndAwait
public Void closeAndAwait(short statusCode)
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- 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- Parameters:
statusCode-
-
close
@CheckReturnValue public io.smallrye.mutiny.Uni<Void> close(short statusCode, String reason)
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- Parameters:
statusCode-reason-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
closeAndAwait
public Void closeAndAwait(short statusCode, String reason)
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- Parameters:
statusCode-reason-- Returns:
- the Void instance produced by the operation.
-
closeAndForget
public void closeAndForget(short statusCode, String reason)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- Parameters:
statusCode-reason-
-
remoteAddress
public SocketAddress remoteAddress()
- Specified by:
remoteAddressin interfaceWebSocketBase- 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
public SocketAddress localAddress()
- Specified by:
localAddressin interfaceWebSocketBase- 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- Returns:
- true if this
HttpConnectionis encrypted via SSL/TLS.
-
isClosed
public boolean isClosed()
- Specified by:
isClosedin interfaceWebSocketBase- Returns:
trueif the WebSocket is closed
-
exceptionHandler
public WebSocket exceptionHandler(Consumer<Throwable> handler)
- Specified by:
exceptionHandlerin interfaceReadStream<Buffer>- Specified by:
exceptionHandlerin interfaceStreamBase- Specified by:
exceptionHandlerin interfaceWebSocketBase- Specified by:
exceptionHandlerin interfaceWriteStream<Buffer>- Parameters:
handler- the exception handler- Returns:
-
handler
public WebSocket handler(Consumer<Buffer> handler)
- Specified by:
handlerin interfaceReadStream<Buffer>- Specified by:
handlerin interfaceWebSocketBase- Returns:
-
pause
public WebSocket pause()
- Specified by:
pausein interfaceReadStream<Buffer>- Specified by:
pausein interfaceWebSocketBase- Returns:
- a reference to this, so the API can be used fluently
-
resume
public WebSocket resume()
- Specified by:
resumein interfaceReadStream<Buffer>- Specified by:
resumein interfaceWebSocketBase- Returns:
- a reference to this, so the API can be used fluently
-
fetch
public WebSocket fetch(long amount)
- Specified by:
fetchin interfaceReadStream<Buffer>- Specified by:
fetchin interfaceWebSocketBase- Returns:
- a reference to this, so the API can be used fluently
-
endHandler
public WebSocket endHandler(Runnable endHandler)
- Specified by:
endHandlerin interfaceReadStream<Buffer>- Specified by:
endHandlerin interfaceWebSocketBase- Returns:
-
setWriteQueueMaxSize
public WebSocket setWriteQueueMaxSize(int maxSize)
- Specified by:
setWriteQueueMaxSizein interfaceWebSocketBase- Specified by:
setWriteQueueMaxSizein interfaceWriteStream<Buffer>- Parameters:
maxSize- the max size of the write stream- Returns:
- a reference to this, so the API can be used fluently
-
drainHandler
public WebSocket drainHandler(Runnable handler)
- Specified by:
drainHandlerin interfaceWebSocketBase- Specified by:
drainHandlerin interfaceWriteStream<Buffer>- Parameters:
handler- the handler- Returns:
-
writeFrame
@CheckReturnValue public io.smallrye.mutiny.Uni<Void> writeFrame(WebSocketFrame frame)
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- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeFrameAndAwait
public Void writeFrameAndAwait(WebSocketFrame frame)
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- Returns:
- the Void instance produced by the operation.
-
writeFrameAndForget
public WebSocket writeFrameAndForget(WebSocketFrame frame)
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- Returns:
- the instance of WebSocketBase to chain method calls.
-
writeFinalTextFrame
@CheckReturnValue public io.smallrye.mutiny.Uni<Void> writeFinalTextFrame(String text)
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- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeFinalTextFrameAndAwait
public Void writeFinalTextFrameAndAwait(String text)
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- Returns:
- the Void instance produced by the operation.
-
writeFinalTextFrameAndForget
public WebSocket writeFinalTextFrameAndForget(String text)
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- Returns:
- the instance of WebSocketBase to chain method calls.
-
writeFinalBinaryFrame
@CheckReturnValue public io.smallrye.mutiny.Uni<Void> writeFinalBinaryFrame(Buffer data)
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- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeFinalBinaryFrameAndAwait
public Void writeFinalBinaryFrameAndAwait(Buffer data)
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- Returns:
- the Void instance produced by the operation.
-
writeFinalBinaryFrameAndForget
public WebSocket writeFinalBinaryFrameAndForget(Buffer data)
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- Returns:
- the instance of WebSocketBase to chain method calls.
-
writeBinaryMessage
@CheckReturnValue public io.smallrye.mutiny.Uni<Void> writeBinaryMessage(Buffer data)
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- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeBinaryMessageAndAwait
public Void writeBinaryMessageAndAwait(Buffer data)
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- Returns:
- the Void instance produced by the operation.
-
writeBinaryMessageAndForget
public WebSocket writeBinaryMessageAndForget(Buffer data)
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- Returns:
- the instance of WebSocketBase to chain method calls.
-
writeTextMessage
@CheckReturnValue public io.smallrye.mutiny.Uni<Void> writeTextMessage(String text)
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- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeTextMessageAndAwait
public Void writeTextMessageAndAwait(String text)
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- Returns:
- the Void instance produced by the operation.
-
writeTextMessageAndForget
public WebSocket writeTextMessageAndForget(String text)
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- Returns:
- the instance of WebSocketBase to chain method calls.
-
closeHandler
public WebSocket closeHandler(Runnable handler)
- Specified by:
closeHandlerin interfaceWebSocketBase- Parameters:
handler- the handler- Returns:
-
frameHandler
public WebSocket frameHandler(Consumer<WebSocketFrame> handler)
- Specified by:
frameHandlerin interfaceWebSocketBase- Parameters:
handler- the handler- Returns:
-
sslSession
public SSLSession sslSession()
- Specified by:
sslSessionin interfaceWebSocketBase- Returns:
- SSLSession associated with the underlying socket. Returns null if connection is not SSL.
-
toMulti
@CheckReturnValue public io.smallrye.mutiny.Multi<Buffer> toMulti()
- Specified by:
toMultiin interfaceReadStream<Buffer>
-
newInstance
public static WebSocket newInstance(io.vertx.core.http.WebSocket arg)
-
-