Interface WebSocketBase
-
- All Superinterfaces:
ReadStream<Buffer>,StreamBase,WriteStream<Buffer>
- All Known Implementing Classes:
ServerWebSocket,WebSocket
public interface WebSocketBase extends ReadStream<Buffer>, WriteStream<Buffer>
Base WebSocket implementation.It implements both and so it can be used with
NOTE: This class has been automatically generated from thePipeto pipe data with flow control.originalnon Mutiny-ified interface using Vert.x codegen.
-
-
Field Summary
Fields Modifier and Type Field Description static TypeArg<Buffer>TYPE_ARG_0
-
Method Summary
All Methods Static Methods Instance Methods Abstract Methods Modifier and Type Method Description StringbinaryHandlerID()WebSocketBasebinaryMessageHandler(Consumer<Buffer> handler)io.smallrye.mutiny.Uni<Void>close()Same asclose()but with anhandlercalled when the operation completesio.smallrye.mutiny.Uni<Void>close(short statusCode)Same asclose()but with anhandlercalled when the operation completesio.smallrye.mutiny.Uni<Void>close(short statusCode, String reason)Same asclose()but with anhandlercalled when the operation completesVoidcloseAndAwait()Blocking variant ofclose().VoidcloseAndAwait(short statusCode)Blocking variant ofclose(short).VoidcloseAndAwait(short statusCode, String reason)Blocking variant ofclose(short,String).voidcloseAndForget()Variant ofclose()that ignores the result of the operation.voidcloseAndForget(short statusCode)Variant ofclose(short)that ignores the result of the operation.voidcloseAndForget(short statusCode, String reason)Variant ofclose(short,String)that ignores the result of the operation.WebSocketBasecloseHandler(Runnable handler)StringcloseReason()ShortcloseStatusCode()WebSocketBasedrainHandler(Runnable handler)io.smallrye.mutiny.Uni<Void>end()Callsclose()io.smallrye.mutiny.Uni<Void>end(Buffer data)Same as but with anhandlercalled when the operation completesVoidendAndAwait()Blocking variant ofend(io.vertx.mutiny.core.buffer.Buffer).VoidendAndAwait(Buffer data)Blocking variant ofio.vertx.mutiny.core.streams.WriteStream#end(io.vertx.mutiny.core.buffer.Buffer).voidendAndForget()Variant ofend(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.WebSocketBaseendHandler(Runnable endHandler)WebSocketBaseexceptionHandler(Consumer<Throwable> handler)WebSocketBasefetch(long amount)WebSocketBaseframeHandler(Consumer<WebSocketFrame> handler)io.vertx.core.http.WebSocketBasegetDelegate()WebSocketBasehandler(Consumer<Buffer> handler)MultiMapheaders()booleanisClosed()booleanisSsl()SocketAddresslocalAddress()static WebSocketBasenewInstance(io.vertx.core.http.WebSocketBase arg)WebSocketBasepause()Pipe<Buffer>pipe()io.smallrye.mutiny.Uni<Void>pipeTo(WriteStream<Buffer> dst)Pipe thisReadStreamto theWriteStream.VoidpipeToAndAwait(WriteStream<Buffer> dst)Blocking variant ofio.vertx.mutiny.core.streams.ReadStream#pipeTo(io.vertx.mutiny.core.streams.WriteStream.) voidpipeToAndForget(WriteStream<Buffer> dst)Variant ofio.vertx.mutiny.core.streams.ReadStream#pipeTo(io.vertx.mutiny.core.streams.WriteStreamthat ignores the result of the operation.) WebSocketBasepongHandler(Consumer<Buffer> handler)SocketAddressremoteAddress()WebSocketBaseresume()WebSocketBasesetWriteQueueMaxSize(int maxSize)SSLSessionsslSession()StringsubProtocol()StringtextHandlerID()WebSocketBasetextMessageHandler(Consumer<String> handler)io.smallrye.mutiny.Uni<Void>write(Buffer data)Same as but with anhandlercalled when the operation completesVoidwriteAndAwait(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 aswriteBinaryMessage(io.vertx.mutiny.core.buffer.Buffer)but with anhandlercalled when the operation completesVoidwriteBinaryMessageAndAwait(Buffer data)Blocking variant ofwriteBinaryMessage(io.vertx.mutiny.core.buffer.Buffer).WebSocketBasewriteBinaryMessageAndForget(Buffer data)Variant ofwriteBinaryMessage(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.io.smallrye.mutiny.Uni<Void>writeFinalBinaryFrame(Buffer data)Same aswriteFinalBinaryFrame(io.vertx.mutiny.core.buffer.Buffer)but with anhandlercalled when the operation completesVoidwriteFinalBinaryFrameAndAwait(Buffer data)Blocking variant ofwriteFinalBinaryFrame(io.vertx.mutiny.core.buffer.Buffer).WebSocketBasewriteFinalBinaryFrameAndForget(Buffer data)Variant ofwriteFinalBinaryFrame(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.io.smallrye.mutiny.Uni<Void>writeFinalTextFrame(String text)Same aswriteFinalTextFrame(java.lang.String)but with anhandlercalled when the operation completesVoidwriteFinalTextFrameAndAwait(String text)Blocking variant ofwriteFinalTextFrame(String).WebSocketBasewriteFinalTextFrameAndForget(String text)Variant ofwriteFinalTextFrame(String)that ignores the result of the operation.io.smallrye.mutiny.Uni<Void>writeFrame(WebSocketFrame frame)Same aswriteFrame(io.vertx.mutiny.core.http.WebSocketFrame)but with anhandlercalled when the operation completesVoidwriteFrameAndAwait(WebSocketFrame frame)Blocking variant ofwriteFrame(io.vertx.mutiny.core.http.WebSocketFrame).WebSocketBasewriteFrameAndForget(WebSocketFrame frame)Variant ofwriteFrame(io.vertx.mutiny.core.http.WebSocketFrame)that ignores the result of the operation.io.smallrye.mutiny.Uni<Void>writePing(Buffer data)Writes a ping frame to the connection.VoidwritePingAndAwait(Buffer data)Blocking variant ofwritePing(io.vertx.mutiny.core.buffer.Buffer).WebSocketBasewritePingAndForget(Buffer data)Variant ofwritePing(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.io.smallrye.mutiny.Uni<Void>writePong(Buffer data)Writes a pong frame to the connection.VoidwritePongAndAwait(Buffer data)Blocking variant ofwritePong(io.vertx.mutiny.core.buffer.Buffer).WebSocketBasewritePongAndForget(Buffer data)Variant ofwritePong(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.booleanwriteQueueFull()io.smallrye.mutiny.Uni<Void>writeTextMessage(String text)Same aswriteTextMessage(java.lang.String)but with anhandlercalled when the operation completesVoidwriteTextMessageAndAwait(String text)Blocking variant ofwriteTextMessage(String).WebSocketBasewriteTextMessageAndForget(String text)Variant ofwriteTextMessage(String)that ignores the result of the operation.-
Methods inherited from interface io.vertx.mutiny.core.streams.ReadStream
toMulti
-
-
-
-
Method Detail
-
getDelegate
io.vertx.core.http.WebSocketBase getDelegate()
- Specified by:
getDelegatein interfaceReadStream<Buffer>- Specified by:
getDelegatein interfaceStreamBase- Specified by:
getDelegatein interfaceWriteStream<Buffer>
-
pipe
Pipe<Buffer> pipe()
- Specified by:
pipein interfaceReadStream<Buffer>- Returns:
- a pipe
-
pipeTo
@CheckReturnValue 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>- Parameters:
dst- the destination write stream- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
pipeToAndAwait
Void pipeToAndAwait(WriteStream<Buffer> dst)
Blocking variant ofio.vertx.mutiny.core.streams.ReadStream#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>- Parameters:
dst- the destination write stream- Returns:
- the Void instance produced by the operation.
-
pipeToAndForget
void pipeToAndForget(WriteStream<Buffer> dst)
Variant ofio.vertx.mutiny.core.streams.ReadStream#pipeTo(io.vertx.mutiny.core.streams.WriteStreamthat ignores the result of the operation.) This method subscribes on the result of
io.vertx.mutiny.core.streams.ReadStream#pipeTo(io.vertx.mutiny.core.streams.WriteStream, but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation from) io.vertx.mutiny.core.streams.ReadStream#pipeTo(io.vertx.mutiny.core.streams.WriteStreambut you don't need to compose it with other operations.) - Specified by:
pipeToAndForgetin interfaceReadStream<Buffer>- Parameters:
dst- the destination write stream
-
write
@CheckReturnValue 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 interfaceWriteStream<Buffer>- Parameters:
data-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeAndAwait
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 interfaceWriteStream<Buffer>- Parameters:
data-- Returns:
- the Void instance produced by the operation.
-
writeAndForget
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 interfaceWriteStream<Buffer>- Parameters:
data-
-
end
@CheckReturnValue 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 interfaceWriteStream<Buffer>- Parameters:
data-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
endAndAwait
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 interfaceWriteStream<Buffer>- Parameters:
data-- Returns:
- the Void instance produced by the operation.
-
endAndForget
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 interfaceWriteStream<Buffer>- Parameters:
data-
-
writeQueueFull
boolean writeQueueFull()
- Specified by:
writeQueueFullin interfaceWriteStream<Buffer>- Returns:
trueif write queue is full
-
exceptionHandler
WebSocketBase exceptionHandler(Consumer<Throwable> handler)
- Specified by:
exceptionHandlerin interfaceReadStream<Buffer>- Specified by:
exceptionHandlerin interfaceStreamBase- Specified by:
exceptionHandlerin interfaceWriteStream<Buffer>- Parameters:
handler- the exception handler- Returns:
-
handler
WebSocketBase handler(Consumer<Buffer> handler)
- Specified by:
handlerin interfaceReadStream<Buffer>- Returns:
-
pause
WebSocketBase pause()
- Specified by:
pausein interfaceReadStream<Buffer>- Returns:
- a reference to this, so the API can be used fluently
-
resume
WebSocketBase resume()
- Specified by:
resumein interfaceReadStream<Buffer>- Returns:
- a reference to this, so the API can be used fluently
-
fetch
WebSocketBase fetch(long amount)
- Specified by:
fetchin interfaceReadStream<Buffer>- Returns:
- a reference to this, so the API can be used fluently
-
endHandler
WebSocketBase endHandler(Runnable endHandler)
- Specified by:
endHandlerin interfaceReadStream<Buffer>- Returns:
-
setWriteQueueMaxSize
WebSocketBase setWriteQueueMaxSize(int maxSize)
- 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
WebSocketBase drainHandler(Runnable handler)
- Specified by:
drainHandlerin interfaceWriteStream<Buffer>- Parameters:
handler- the handler- Returns:
-
binaryHandlerID
String binaryHandlerID()
- Returns:
- the binary handler id
-
textHandlerID
String textHandlerID()
- Returns:
-
subProtocol
String subProtocol()
- Returns:
-
closeStatusCode
Short closeStatusCode()
- Returns:
-
closeReason
String closeReason()
- Returns:
-
headers
MultiMap headers()
- Returns:
- the headers
-
writeFrame
@CheckReturnValue io.smallrye.mutiny.Uni<Void> writeFrame(WebSocketFrame frame)
Same aswriteFrame(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.- Parameters:
frame-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeFrameAndAwait
Void writeFrameAndAwait(WebSocketFrame frame)
Blocking variant ofwriteFrame(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).
- Parameters:
frame-- Returns:
- the Void instance produced by the operation.
-
writeFrameAndForget
WebSocketBase writeFrameAndForget(WebSocketFrame frame)
Variant ofwriteFrame(io.vertx.mutiny.core.http.WebSocketFrame)that ignores the result of the operation.This method subscribes on the result of
writeFrame(io.vertx.mutiny.core.http.WebSocketFrame), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromwriteFrame(io.vertx.mutiny.core.http.WebSocketFrame)but you don't need to compose it with other operations.- Parameters:
frame-- Returns:
- the instance of WebSocketBase to chain method calls.
-
writeFinalTextFrame
@CheckReturnValue io.smallrye.mutiny.Uni<Void> writeFinalTextFrame(String text)
Same aswriteFinalTextFrame(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.- Parameters:
text-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeFinalTextFrameAndAwait
Void writeFinalTextFrameAndAwait(String text)
Blocking variant ofwriteFinalTextFrame(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:
text-- Returns:
- the Void instance produced by the operation.
-
writeFinalTextFrameAndForget
WebSocketBase writeFinalTextFrameAndForget(String text)
Variant ofwriteFinalTextFrame(String)that ignores the result of the operation.This method subscribes on the result of
writeFinalTextFrame(String), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromwriteFinalTextFrame(String)but you don't need to compose it with other operations.- Parameters:
text-- Returns:
- the instance of WebSocketBase to chain method calls.
-
writeFinalBinaryFrame
@CheckReturnValue io.smallrye.mutiny.Uni<Void> writeFinalBinaryFrame(Buffer data)
Same aswriteFinalBinaryFrame(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.- Parameters:
data-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeFinalBinaryFrameAndAwait
Void writeFinalBinaryFrameAndAwait(Buffer data)
Blocking variant ofwriteFinalBinaryFrame(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).
- Parameters:
data-- Returns:
- the Void instance produced by the operation.
-
writeFinalBinaryFrameAndForget
WebSocketBase writeFinalBinaryFrameAndForget(Buffer data)
Variant ofwriteFinalBinaryFrame(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.This method subscribes on the result of
writeFinalBinaryFrame(io.vertx.mutiny.core.buffer.Buffer), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromwriteFinalBinaryFrame(io.vertx.mutiny.core.buffer.Buffer)but you don't need to compose it with other operations.- Parameters:
data-- Returns:
- the instance of WebSocketBase to chain method calls.
-
writeBinaryMessage
@CheckReturnValue io.smallrye.mutiny.Uni<Void> writeBinaryMessage(Buffer data)
Same aswriteBinaryMessage(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.- Parameters:
data-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeBinaryMessageAndAwait
Void writeBinaryMessageAndAwait(Buffer data)
Blocking variant ofwriteBinaryMessage(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).
- Parameters:
data-- Returns:
- the Void instance produced by the operation.
-
writeBinaryMessageAndForget
WebSocketBase writeBinaryMessageAndForget(Buffer data)
Variant ofwriteBinaryMessage(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.This method subscribes on the result of
writeBinaryMessage(io.vertx.mutiny.core.buffer.Buffer), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromwriteBinaryMessage(io.vertx.mutiny.core.buffer.Buffer)but you don't need to compose it with other operations.- Parameters:
data-- Returns:
- the instance of WebSocketBase to chain method calls.
-
writeTextMessage
@CheckReturnValue io.smallrye.mutiny.Uni<Void> writeTextMessage(String text)
Same aswriteTextMessage(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.- Parameters:
text-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
writeTextMessageAndAwait
Void writeTextMessageAndAwait(String text)
Blocking variant ofwriteTextMessage(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:
text-- Returns:
- the Void instance produced by the operation.
-
writeTextMessageAndForget
WebSocketBase writeTextMessageAndForget(String text)
Variant ofwriteTextMessage(String)that ignores the result of the operation.This method subscribes on the result of
writeTextMessage(String), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromwriteTextMessage(String)but you don't need to compose it with other operations.- Parameters:
text-- Returns:
- the instance of WebSocketBase to chain method calls.
-
writePing
@CheckReturnValue 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.- 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
Void writePingAndAwait(Buffer data)
Blocking variant ofwritePing(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).
- Parameters:
data- the data to write, may be at most 125 bytes- Returns:
- the Void instance produced by the operation.
-
writePingAndForget
WebSocketBase writePingAndForget(Buffer data)
Variant ofwritePing(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.This method subscribes on the result of
writePing(io.vertx.mutiny.core.buffer.Buffer), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromwritePing(io.vertx.mutiny.core.buffer.Buffer)but you don't need to compose it with other operations.- Parameters:
data- the data to write, may be at most 125 bytes- Returns:
- the instance of WebSocketBase to chain method calls.
-
writePong
@CheckReturnValue 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.- 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
Void writePongAndAwait(Buffer data)
Blocking variant ofwritePong(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).
- Parameters:
data- the data to write, may be at most 125 bytes- Returns:
- the Void instance produced by the operation.
-
writePongAndForget
WebSocketBase writePongAndForget(Buffer data)
Variant ofwritePong(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.This method subscribes on the result of
writePong(io.vertx.mutiny.core.buffer.Buffer), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromwritePong(io.vertx.mutiny.core.buffer.Buffer)but you don't need to compose it with other operations.- Parameters:
data- the data to write, may be at most 125 bytes- Returns:
- the instance of WebSocketBase to chain method calls.
-
closeHandler
WebSocketBase closeHandler(Runnable handler)
- Parameters:
handler- the handler- Returns:
-
frameHandler
WebSocketBase frameHandler(Consumer<WebSocketFrame> handler)
- Parameters:
handler- the handler- Returns:
-
textMessageHandler
WebSocketBase textMessageHandler(Consumer<String> handler)
- Parameters:
handler- the handler- Returns:
-
binaryMessageHandler
WebSocketBase binaryMessageHandler(Consumer<Buffer> handler)
- Parameters:
handler- the handler- Returns:
-
pongHandler
WebSocketBase pongHandler(Consumer<Buffer> handler)
- Parameters:
handler- the handler- Returns:
-
end
@CheckReturnValue io.smallrye.mutiny.Uni<Void> end()
Callsclose()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 interfaceWriteStream<Buffer>- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
endAndAwait
Void endAndAwait()
Blocking variant ofend(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 interfaceWriteStream<Buffer>- Returns:
- the Void instance produced by the operation.
-
endAndForget
void endAndForget()
Variant ofend(io.vertx.mutiny.core.buffer.Buffer)that ignores the result of the operation.This method subscribes on the result of
end(io.vertx.mutiny.core.buffer.Buffer), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromend(io.vertx.mutiny.core.buffer.Buffer)but you don't need to compose it with other operations.- Specified by:
endAndForgetin interfaceWriteStream<Buffer>
-
close
@CheckReturnValue io.smallrye.mutiny.Uni<Void> close()
Same asclose()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.- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
closeAndAwait
Void closeAndAwait()
Blocking variant ofclose().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).
- Returns:
- the Void instance produced by the operation.
-
closeAndForget
void closeAndForget()
-
close
@CheckReturnValue io.smallrye.mutiny.Uni<Void> close(short statusCode)
Same asclose()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.- Parameters:
statusCode-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
closeAndAwait
Void closeAndAwait(short statusCode)
Blocking variant ofclose(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).
- Parameters:
statusCode-- Returns:
- the Void instance produced by the operation.
-
closeAndForget
void closeAndForget(short statusCode)
Variant ofclose(short)that ignores the result of the operation.This method subscribes on the result of
close(short), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromclose(short)but you don't need to compose it with other operations.- Parameters:
statusCode-
-
close
@CheckReturnValue io.smallrye.mutiny.Uni<Void> close(short statusCode, String reason)
Same asclose()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.- Parameters:
statusCode-reason-- Returns:
- the
unifiring the result of the operation when completed, or a failure if the operation failed.
-
closeAndAwait
Void closeAndAwait(short statusCode, String reason)
Blocking variant ofclose(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).
- Parameters:
statusCode-reason-- Returns:
- the Void instance produced by the operation.
-
closeAndForget
void closeAndForget(short statusCode, String reason)Variant ofclose(short,String)that ignores the result of the operation.This method subscribes on the result of
close(short,String), but discards the outcome (item or failure). This method is useful to trigger the asynchronous operation fromclose(short,String)but you don't need to compose it with other operations.- Parameters:
statusCode-reason-
-
remoteAddress
SocketAddress remoteAddress()
- 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
SocketAddress localAddress()
- 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
boolean isSsl()
- Returns:
- true if this
HttpConnectionis encrypted via SSL/TLS.
-
isClosed
boolean isClosed()
- Returns:
trueif the WebSocket is closed
-
sslSession
SSLSession sslSession()
- Returns:
- SSLSession associated with the underlying socket. Returns null if connection is not SSL.
-
newInstance
static WebSocketBase newInstance(io.vertx.core.http.WebSocketBase arg)
-
-