Package io.vertx.mutiny.core.http

Class WebSocketBase.WebSocketBaseImpl

java.lang.Object
io.vertx.mutiny.core.http.WebSocketBase.WebSocketBaseImpl
All Implemented Interfaces:
MutinyDelegate, WebSocketBase, ReadStream<io.vertx.core.buffer.Buffer>, StreamBase, WriteStream<io.vertx.core.buffer.Buffer>
Enclosing interface:
WebSocketBase
public static class WebSocketBase.WebSocketBaseImpl extends Object implements WebSocketBase

  • Constructor Details

    • WebSocketBaseImpl

      public WebSocketBaseImpl(io.vertx.core.http.WebSocketBase delegate)
      Create a new instance of WebSocketBase.WebSocketBaseImpl delegating to the given (non-null) instance of WebSocketBase.

  • Method Details

    • getDelegate

      public io.vertx.core.http.WebSocketBase getDelegate()
      Get the delegate instance.

      This method returns the instance on which this shim is delegating the calls. And so, give you access to the bare API.

      Specified by:
      getDelegate in interface MutinyDelegate
      Specified by:
      getDelegate in interface ReadStream<io.vertx.core.buffer.Buffer>
      Specified by:
      getDelegate in interface StreamBase
      Specified by:
      getDelegate in interface WebSocketBase
      Specified by:
      getDelegate in interface WriteStream<io.vertx.core.buffer.Buffer>
      Returns:
      the delegate instance

    • writeFrame

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> writeFrame(io.vertx.core.http.WebSocketFrame frame)
      Write a WebSocket frame to the connection

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      writeFrame in interface WebSocketBase
      Parameters:
      frame - the frame to write
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.writeFrame(WebSocketFrame)

    • writeFrameAndAwait

      public void writeFrameAndAwait(io.vertx.core.http.WebSocketFrame frame)
      Write a WebSocket frame to the connection

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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 - the frame to write
      See Also:
      • WebSocketBase.writeFrame(WebSocketFrame)

    • writeFrameAndForget

      public WebSocketBase.WebSocketBaseImpl writeFrameAndForget(io.vertx.core.http.WebSocketFrame frame)
      Write a WebSocket frame to the connection

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Parameters:
      frame - the frame to write
      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.writeFrame(WebSocketFrame)

    • writeFinalTextFrame

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> writeFinalTextFrame(String text)
      Write a final WebSocket text frame to the connection

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      writeFinalTextFrame in interface WebSocketBase
      Parameters:
      text - The text to write
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.writeFinalTextFrame(String)

    • writeFinalTextFrameAndAwait

      public void writeFinalTextFrameAndAwait(String text)
      Write a final WebSocket text frame to the connection

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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 - The text to write
      See Also:
      • WebSocketBase.writeFinalTextFrame(String)

    • writeFinalTextFrameAndForget

      public WebSocketBase.WebSocketBaseImpl writeFinalTextFrameAndForget(String text)
      Write a final WebSocket text frame to the connection

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Parameters:
      text - The text to write
      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.writeFinalTextFrame(String)

    • writeFinalBinaryFrame

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> writeFinalBinaryFrame(io.vertx.core.buffer.Buffer data)
      Write a final WebSocket binary frame to the connection

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      writeFinalBinaryFrame in interface WebSocketBase
      Parameters:
      data - The data to write
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.writeFinalBinaryFrame(Buffer)

    • writeFinalBinaryFrameAndAwait

      public void writeFinalBinaryFrameAndAwait(io.vertx.core.buffer.Buffer data)
      Write a final WebSocket binary frame to the connection

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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
      See Also:
      • WebSocketBase.writeFinalBinaryFrame(Buffer)

    • writeFinalBinaryFrameAndForget

      public WebSocketBase.WebSocketBaseImpl writeFinalBinaryFrameAndForget(io.vertx.core.buffer.Buffer data)
      Write a final WebSocket binary frame to the connection

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Parameters:
      data - The data to write
      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.writeFinalBinaryFrame(Buffer)

    • writeBinaryMessage

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> writeBinaryMessage(io.vertx.core.buffer.Buffer data)
      Writes a (potentially large) piece of binary data to the connection. This data might be written as multiple frames if it exceeds the maximum WebSocket frame size.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      writeBinaryMessage in interface WebSocketBase
      Parameters:
      data - the data to write
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.writeBinaryMessage(Buffer)

    • writeBinaryMessageAndAwait

      public void writeBinaryMessageAndAwait(io.vertx.core.buffer.Buffer data)
      Writes a (potentially large) piece of binary data to the connection. This data might be written as multiple frames if it exceeds the maximum WebSocket frame size.

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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
      See Also:
      • WebSocketBase.writeBinaryMessage(Buffer)

    • writeBinaryMessageAndForget

      public WebSocketBase.WebSocketBaseImpl writeBinaryMessageAndForget(io.vertx.core.buffer.Buffer data)
      Writes a (potentially large) piece of binary data to the connection. This data might be written as multiple frames if it exceeds the maximum WebSocket frame size.

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Parameters:
      data - the data to write
      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.writeBinaryMessage(Buffer)

    • writeTextMessage

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> writeTextMessage(String text)
      Writes a (potentially large) piece of text data to the connection. This data might be written as multiple frames if it exceeds the maximum WebSocket frame size.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      writeTextMessage in interface WebSocketBase
      Parameters:
      text - the data to write
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.writeTextMessage(String)

    • writeTextMessageAndAwait

      public void writeTextMessageAndAwait(String text)
      Writes a (potentially large) piece of text data to the connection. This data might be written as multiple frames if it exceeds the maximum WebSocket frame size.

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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 - the data to write
      See Also:
      • WebSocketBase.writeTextMessage(String)

    • writeTextMessageAndForget

      public WebSocketBase.WebSocketBaseImpl writeTextMessageAndForget(String text)
      Writes a (potentially large) piece of text data to the connection. This data might be written as multiple frames if it exceeds the maximum WebSocket frame size.

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Parameters:
      text - the data to write
      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.writeTextMessage(String)

    • writePing

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> writePing(io.vertx.core.buffer.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. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      writePing in interface WebSocketBase
      Parameters:
      data - the data to write, may be at most 125 bytes
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.writePing(Buffer)

    • writePingAndAwait

      public void writePingAndAwait(io.vertx.core.buffer.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 Void. This method awaits indefinitely 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
      See Also:
      • WebSocketBase.writePing(Buffer)

    • writePingAndForget

      public WebSocketBase.WebSocketBaseImpl writePingAndForget(io.vertx.core.buffer.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 ignores the Void result or any failure.

      Parameters:
      data - the data to write, may be at most 125 bytes
      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.writePing(Buffer)

    • writePong

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> writePong(io.vertx.core.buffer.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. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      writePong in interface WebSocketBase
      Parameters:
      data - the data to write, may be at most 125 bytes
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.writePong(Buffer)

    • writePongAndAwait

      public void writePongAndAwait(io.vertx.core.buffer.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 Void. This method awaits indefinitely 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
      See Also:
      • WebSocketBase.writePong(Buffer)

    • writePongAndForget

      public WebSocketBase.WebSocketBaseImpl writePongAndForget(io.vertx.core.buffer.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 ignores the Void result or any failure.

      Parameters:
      data - the data to write, may be at most 125 bytes
      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.writePong(Buffer)

    • end

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> end()
      Ends the stream.

      Once the stream has ended, it cannot be used any more.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Calls WebSocketBase.close()

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Calls close()

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      end in interface WebSocketBase
      Specified by:
      end in interface WriteStream<io.vertx.core.buffer.Buffer>
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.end()

    • endAndAwait

      public void endAndAwait()
      Calls close()

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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).

      See Also:
      • WebSocketBase.end()

    • endAndForget

      public WebSocketBase.WebSocketBaseImpl endAndForget()
      Calls close()

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.end()

    • close

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> close()
      Close the WebSocket sending the default close frame.

      No more messages can be sent.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      close in interface WebSocketBase
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.close()

    • closeAndAwait

      public void closeAndAwait()
      Close the WebSocket sending the default close frame.

      No more messages can be sent.

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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).

      See Also:
      • WebSocketBase.close()

    • closeAndForget

      public WebSocketBase.WebSocketBaseImpl closeAndForget()
      Close the WebSocket sending the default close frame.

      No more messages can be sent.

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.close()

    • close

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> close(short statusCode)
      Close the WebSocket sending a close frame with specified status code. You can give a look at various close payloads here: RFC6455 section 7.4.1

      No more messages can be sent.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      close in interface WebSocketBase
      Parameters:
      statusCode - the status code
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.close(short)

    • closeAndAwait

      public void closeAndAwait(short statusCode)
      Close the WebSocket sending a close frame with specified status code. You can give a look at various close payloads here: RFC6455 section 7.4.1

      No more messages can be sent.

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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 - the status code
      See Also:
      • WebSocketBase.close(short)

    • closeAndForget

      public WebSocketBase.WebSocketBaseImpl closeAndForget(short statusCode)
      Close the WebSocket sending a close frame with specified status code. You can give a look at various close payloads here: RFC6455 section 7.4.1

      No more messages can be sent.

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Parameters:
      statusCode - the status code
      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.close(short)

    • close

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> close(short statusCode, String reason)
      Close sending a close frame with specified status code and reason. You can give a look at various close payloads here: RFC6455 section 7.4.1

      No more messages can be sent.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      close in interface WebSocketBase
      Parameters:
      statusCode - the status code
      reason - reason of closure. Can be null.
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.close(short, String)

    • closeAndAwait

      public void closeAndAwait(short statusCode, String reason)
      Close sending a close frame with specified status code and reason. You can give a look at various close payloads here: RFC6455 section 7.4.1

      No more messages can be sent.

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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 - the status code
      reason - reason of closure
      See Also:
      • WebSocketBase.close(short, String)

    • closeAndForget

      public WebSocketBase.WebSocketBaseImpl closeAndForget(short statusCode, String reason)
      Close sending a close frame with specified status code and reason. You can give a look at various close payloads here: RFC6455 section 7.4.1

      No more messages can be sent.

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Parameters:
      statusCode - the status code
      reason - reason of closure
      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.close(short, String)

    • shutdown

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> shutdown()
      Like shutdown(long, TimeUnit, short, String) with a 30 seconds timeout, the status code 1000 a null reason.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      shutdown in interface WebSocketBase
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.shutdown()

    • shutdownAndAwait

      public void shutdownAndAwait()
      Like shutdown(long, TimeUnit, short, String) with a 30 seconds timeout, the status code 1000 a null reason.

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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).

      See Also:
      • WebSocketBase.shutdown()

    • shutdownAndForget

      public WebSocketBase.WebSocketBaseImpl shutdownAndForget()
      Like shutdown(long, TimeUnit, short, String) with a 30 seconds timeout, the status code 1000 a null reason.

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.shutdown()

    • shutdown

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> shutdown(short statusCode)
      Like shutdown(long, TimeUnit, short, String) with a 30 seconds timeout and a null reason.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      shutdown in interface WebSocketBase
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.shutdown(short)

    • shutdownAndAwait

      public void shutdownAndAwait(short statusCode)
      Like shutdown(long, TimeUnit, short, String) with a 30 seconds timeout and a null reason.

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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).

      See Also:
      • WebSocketBase.shutdown(short)

    • shutdownAndForget

      public WebSocketBase.WebSocketBaseImpl shutdownAndForget(short statusCode)
      Like shutdown(long, TimeUnit, short, String) with a 30 seconds timeout and a null reason.

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.shutdown(short)

    • shutdown

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> shutdown(short statusCode, String reason)
      Like shutdown(long, TimeUnit, short, String) with a 30 seconds timeout.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      shutdown in interface WebSocketBase
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.shutdown(short, String)

    • shutdownAndAwait

      public void shutdownAndAwait(short statusCode, String reason)
      Like shutdown(long, TimeUnit, short, String) with a 30 seconds timeout.

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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).

      See Also:
      • WebSocketBase.shutdown(short, String)

    • shutdownAndForget

      public WebSocketBase.WebSocketBaseImpl shutdownAndForget(short statusCode, String reason)
      Like shutdown(long, TimeUnit, short, String) with a 30 seconds timeout.

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.shutdown(short, String)

    • shutdown

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> shutdown(long timeout, TimeUnit unit)
      Calls shutdown(long, TimeUnit, short, String) with the status code 1000 and a null reason.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      shutdown in interface WebSocketBase
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.shutdown(long, TimeUnit)

    • shutdownAndAwait

      public void shutdownAndAwait(long timeout, TimeUnit unit)
      Calls shutdown(long, TimeUnit, short, String) with the status code 1000 and a null reason.

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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).

      See Also:
      • WebSocketBase.shutdown(long, TimeUnit)

    • shutdownAndForget

      public WebSocketBase.WebSocketBaseImpl shutdownAndForget(long timeout, TimeUnit unit)
      Calls shutdown(long, TimeUnit, short, String) with the status code 1000 and a null reason.

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.shutdown(long, TimeUnit)

    • shutdown

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> shutdown(Duration timeout)
      Calls shutdown(Duration, short, String) with the status code 1000 and a null reason.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      shutdown in interface WebSocketBase
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.shutdown(Duration)

    • shutdownAndAwait

      public void shutdownAndAwait(Duration timeout)
      Calls shutdown(Duration, short, String) with the status code 1000 and a null reason.

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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).

      See Also:
      • WebSocketBase.shutdown(Duration)

    • shutdownAndForget

      public WebSocketBase.WebSocketBaseImpl shutdownAndForget(Duration timeout)
      Calls shutdown(Duration, short, String) with the status code 1000 and a null reason.

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.shutdown(Duration)

    • shutdown

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> shutdown(long timeout, TimeUnit unit, short statusCode)
      Calls shutdown(long, TimeUnit, short, String) with a null reason.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      shutdown in interface WebSocketBase
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.shutdown(long, TimeUnit, short)

    • shutdownAndAwait

      public void shutdownAndAwait(long timeout, TimeUnit unit, short statusCode)
      Calls shutdown(long, TimeUnit, short, String) with a null reason.

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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).

      See Also:
      • WebSocketBase.shutdown(long, TimeUnit, short)

    • shutdownAndForget

      public WebSocketBase.WebSocketBaseImpl shutdownAndForget(long timeout, TimeUnit unit, short statusCode)
      Calls shutdown(long, TimeUnit, short, String) with a null reason.

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.shutdown(long, TimeUnit, short)

    • shutdown

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> shutdown(Duration timeout, short statusCode)
      Calls shutdown(Duration, short, String) with a null reason.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      shutdown in interface WebSocketBase
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.shutdown(Duration, short)

    • shutdownAndAwait

      public void shutdownAndAwait(Duration timeout, short statusCode)
      Calls shutdown(Duration, short, String) with a null reason.

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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).

      See Also:
      • WebSocketBase.shutdown(Duration, short)

    • shutdownAndForget

      public WebSocketBase.WebSocketBaseImpl shutdownAndForget(Duration timeout, short statusCode)
      Calls shutdown(Duration, short, String) with a null reason.

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.shutdown(Duration, short)

    • shutdown

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> shutdown(long timeout, TimeUnit unit, short statusCode, String reason)
      Calls shutdown(Duration, short, String)

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      shutdown in interface WebSocketBase
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.shutdown(long, TimeUnit, short, String)

    • shutdownAndAwait

      public void shutdownAndAwait(long timeout, TimeUnit unit, short statusCode, String reason)
      Calls shutdown(Duration, short, String)

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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).

      See Also:
      • WebSocketBase.shutdown(long, TimeUnit, short, String)

    • shutdownAndForget

      public WebSocketBase.WebSocketBaseImpl shutdownAndForget(long timeout, TimeUnit unit, short statusCode, String reason)
      Calls shutdown(Duration, short, String)

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.shutdown(long, TimeUnit, short, String)

    • shutdown

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> shutdown(Duration timeout, short statusCode, String reason)
      Initiate a graceful WebSocket shutdown, the shutdown handler is notified and shall close the WebSocket, otherwise after a timeout the WebSocket will be closed.

      The WebSocket is closed with specified status code and reason. You can give a look at various close payloads here: RFC6455 section 7.4.1

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      shutdown in interface WebSocketBase
      Parameters:
      timeout - the amount of time after which all resources are forcibly closed
      statusCode - the status code
      reason - reason of closure. Can be null.
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WebSocketBase.shutdown(Duration, short, String)

    • shutdownAndAwait

      public void shutdownAndAwait(Duration timeout, short statusCode, String reason)
      Initiate a graceful WebSocket shutdown, the shutdown handler is notified and shall close the WebSocket, otherwise after a timeout the WebSocket will be closed.

      The WebSocket is closed with specified status code and reason. You can give a look at various close payloads here: RFC6455 section 7.4.1

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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:
      timeout - the amount of time after which all resources are forcibly closed
      statusCode - the status code
      reason - reason of closure
      See Also:
      • WebSocketBase.shutdown(Duration, short, String)

    • shutdownAndForget

      public WebSocketBase.WebSocketBaseImpl shutdownAndForget(Duration timeout, short statusCode, String reason)
      Initiate a graceful WebSocket shutdown, the shutdown handler is notified and shall close the WebSocket, otherwise after a timeout the WebSocket will be closed.

      The WebSocket is closed with specified status code and reason. You can give a look at various close payloads here: RFC6455 section 7.4.1

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Parameters:
      timeout - the amount of time after which all resources are forcibly closed
      statusCode - the status code
      reason - reason of closure
      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WebSocketBase.shutdown(Duration, short, String)

    • write

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> write(io.vertx.core.buffer.Buffer arg0)
      Write some data to the stream.

      The data is usually put on an internal write queue, and the write actually happens asynchronously. To avoid running out of memory by putting too much on the write queue, check the writeQueueFull() method before writing. This is done automatically if using a Pipe.

      When the data is moved from the queue to the actual medium, the returned Future will be completed with the write result, e.g the uni is succeeded when a server HTTP response buffer is written to the socket and failed if the remote client has closed the socket while the data was still pending for write.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      write in interface WebSocketBase
      Specified by:
      write in interface WriteStream<io.vertx.core.buffer.Buffer>
      Parameters:
      data - the data to write
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WriteStream.write(T)

    • writeAndAwait

      public void writeAndAwait(io.vertx.core.buffer.Buffer arg0)
      Write some data to the stream.

      The data is usually put on an internal write queue, and the write actually happens asynchronously. To avoid running out of memory by putting too much on the write queue, check the writeQueueFull() method before writing. This is done automatically if using a Pipe.

      When the data is moved from the queue to the actual medium, the returned Future will be completed with the write result, e.g the underlying uni is succeeded when a server HTTP response buffer is written to the socket and failed if the remote client has closed the socket while the data was still pending for write.

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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
      See Also:
      • WriteStream.write(T)

    • writeAndForget

      public WebSocketBase.WebSocketBaseImpl writeAndForget(io.vertx.core.buffer.Buffer arg0)
      Write some data to the stream.

      The data is usually put on an internal write queue, and the write actually happens asynchronously. To avoid running out of memory by putting too much on the write queue, check the writeQueueFull() method before writing. This is done automatically if using a Pipe.

      When the data is moved from the queue to the actual medium, the returned Future will be completed with the write result, e.g the underlying uni is succeeded when a server HTTP response buffer is written to the socket and failed if the remote client has closed the socket while the data was still pending for write.

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Parameters:
      data - the data to write
      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WriteStream.write(T)

    • pipeTo

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> pipeTo(WriteStream<io.vertx.core.buffer.Buffer> arg0)
      Pipe this ReadStream to the WriteStream.

      Elements emitted by this stream will be written to the write stream until this stream ends or fails.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      pipeTo in interface ReadStream<io.vertx.core.buffer.Buffer>
      Specified by:
      pipeTo in interface WebSocketBase
      Parameters:
      dst - the destination write stream
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • io.vertx.core.http.WebSocketBase#pipeTo(WriteStream)

    • pipeToAndAwait

      public void pipeToAndAwait(WriteStream<io.vertx.core.buffer.Buffer> arg0)
      Pipe this ReadStream to the WriteStream.

      Elements emitted by this stream will be written to the write stream until this stream ends or fails.

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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:
      dst - the destination write stream
      See Also:
      • io.vertx.core.http.WebSocketBase#pipeTo(WriteStream)

    • pipeToAndForget

      public WebSocketBase.WebSocketBaseImpl pipeToAndForget(WriteStream<io.vertx.core.buffer.Buffer> arg0)
      Pipe this ReadStream to the WriteStream.

      Elements emitted by this stream will be written to the write stream until this stream ends or fails.

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Parameters:
      dst - the destination write stream
      Returns:
      The current instance to chain operations if needed.
      See Also:
      • io.vertx.core.http.WebSocketBase#pipeTo(WriteStream)

    • end

      @CheckReturnValue public io.smallrye.mutiny.Uni<Void> end(io.vertx.core.buffer.Buffer arg0)
      Same as end() but writes some data to the stream before ending.

      Unlike the bare Vert.x variant, this method returns a Uni. The uni emits the result of the operation as item. If the operation fails, the uni emits the failure.

      Don't forget to subscribe on it to trigger the operation.

      Specified by:
      end in interface WebSocketBase
      Specified by:
      end in interface WriteStream<io.vertx.core.buffer.Buffer>
      Parameters:
      data - the data to write
      Returns:
      A Uni representing the asynchronous result of this operation.
      See Also:
      • WriteStream.end(T)

    • endAndAwait

      public void endAndAwait(io.vertx.core.buffer.Buffer arg0)
      Same as end() but writes some data to the stream before ending.

      Unlike the bare Vert.x variant, this method returns a Void. This method awaits indefinitely 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
      See Also:
      • WriteStream.end(T)

    • endAndForget

      public WebSocketBase.WebSocketBaseImpl endAndForget(io.vertx.core.buffer.Buffer arg0)
      Same as end() but writes some data to the stream before ending.

      Unlike the bare Vert.x variant, this method ignores the Void result or any failure.

      Parameters:
      data - the data to write
      Returns:
      The current instance to chain operations if needed.
      See Also:
      • WriteStream.end(T)

    • exceptionHandler

      public WebSocketBase exceptionHandler(Consumer<Throwable> handler)
      Description copied from interface: ReadStream
      Set an exception handler on the read stream.
      Specified by:
      exceptionHandler in interface ReadStream<io.vertx.core.buffer.Buffer>
      Specified by:
      exceptionHandler in interface StreamBase
      Specified by:
      exceptionHandler in interface WebSocketBase
      Specified by:
      exceptionHandler in interface WriteStream<io.vertx.core.buffer.Buffer>
      Parameters:
      handler - the exception handler. Can be null.
      Returns:
      a reference to this, so the API can be used fluently

    • handler

      public WebSocketBase handler(Consumer<io.vertx.core.buffer.Buffer> handler)
      Description copied from interface: ReadStream
      Set a data handler. As data is read, the handler will be called with the data.
      Specified by:
      handler in interface ReadStream<io.vertx.core.buffer.Buffer>
      Specified by:
      handler in interface WebSocketBase
      Returns:
      a reference to this, so the API can be used fluently

    • pause

      public WebSocketBase pause()
      Description copied from interface: ReadStream
      Pause the ReadStream, it sets the buffer in fetch mode and clears the actual demand.

      While it's paused, no data will be sent to the data handler.

      Specified by:
      pause in interface ReadStream<io.vertx.core.buffer.Buffer>
      Specified by:
      pause in interface WebSocketBase
      Returns:
      a reference to this, so the API can be used fluently

    • resume

      public WebSocketBase resume()
      Description copied from interface: ReadStream
      Resume reading, and sets the buffer in flowing mode.

      If the ReadStream has been paused, reading will recommence on it.

      Specified by:
      resume in interface ReadStream<io.vertx.core.buffer.Buffer>
      Specified by:
      resume in interface WebSocketBase
      Returns:
      a reference to this, so the API can be used fluently

    • fetch

      public WebSocketBase fetch(long amount)
      Description copied from interface: ReadStream
      Fetch the specified amount of elements. If the ReadStream has been paused, reading will recommence with the specified amount of items, otherwise the specified amount will be added to the current stream demand.
      Specified by:
      fetch in interface ReadStream<io.vertx.core.buffer.Buffer>
      Specified by:
      fetch in interface WebSocketBase
      Returns:
      a reference to this, so the API can be used fluently

    • endHandler

      public WebSocketBase endHandler(Runnable endHandler)
      Description copied from interface: ReadStream
      Set an end handler. Once the stream has ended, and there is no more data to be read, this handler will be called.
      Specified by:
      endHandler in interface ReadStream<io.vertx.core.buffer.Buffer>
      Specified by:
      endHandler in interface WebSocketBase
      Returns:
      a reference to this, so the API can be used fluently

    • setWriteQueueMaxSize

      public WebSocketBase setWriteQueueMaxSize(int maxSize)
      Description copied from interface: WriteStream
      Set the maximum size of the write queue to maxSize. You will still be able to write to the stream even if there is more than maxSize items in the write queue. This is used as an indicator by classes such as Pipe to provide flow control.

      The value is defined by the implementation of the stream, e.g in bytes for a NetSocket, etc...

      Specified by:
      setWriteQueueMaxSize in interface WebSocketBase
      Specified by:
      setWriteQueueMaxSize in interface WriteStream<io.vertx.core.buffer.Buffer>
      Parameters:
      maxSize - the max size of the write stream
      Returns:
      a reference to this, so the API can be used fluently

    • drainHandler

      public WebSocketBase drainHandler(Runnable handler)
      Description copied from interface: WriteStream
      Set a drain handler on the stream. If the write queue is full, then the handler will be called when the write queue is ready to accept buffers again. See Pipe for an example of this being used.

      The stream implementation defines when the drain handler, for example it could be when the queue size has been reduced to maxSize / 2.

      Specified by:
      drainHandler in interface WebSocketBase
      Specified by:
      drainHandler in interface WriteStream<io.vertx.core.buffer.Buffer>
      Parameters:
      handler - the handler. Can be null.
      Returns:
      a reference to this, so the API can be used fluently

    • binaryHandlerID

      public String binaryHandlerID()
      When a WebSocket is created, it may register an event handler with the event bus - the ID of that handler is given by this method.

      By default, no handler is registered, the feature must be enabled via WebSocketConnectOptions#setRegisterWriteHandlers(boolean) or HttpServerOptions#setRegisterWebSocketWriteHandlers(boolean).

      Given this ID, a different event loop can send a binary frame to that event handler using the event bus and that buffer will be received by this instance in its own event loop and written to the underlying connection. This allows you to write data to other WebSockets which are owned by different event loops.

      Specified by:
      binaryHandlerID in interface WebSocketBase
      Returns:
      the binary handler id
      See Also:
      • WebSocketConnectOptions#setRegisterWriteHandlers(boolean)
      • HttpServerOptions#setRegisterWebSocketWriteHandlers(boolean)

    • textHandlerID

      public String textHandlerID()
      When a WebSocket is created, it may register an event handler with the eventbus, the ID of that handler is given by textHandlerID.

      By default, no handler is registered, the feature must be enabled via WebSocketConnectOptions#setRegisterWriteHandlers(boolean) or HttpServerOptions#setRegisterWebSocketWriteHandlers(boolean).

      Given this ID, a different event loop can send a text frame to that event handler using the event bus and that buffer will be received by this instance in its own event loop and written to the underlying connection. This allows you to write data to other WebSockets which are owned by different event loops.

      Specified by:
      textHandlerID in interface WebSocketBase
      Returns:
      the text handler id
      See Also:
      • WebSocketConnectOptions#setRegisterWriteHandlers(boolean)
      • HttpServerOptions#setRegisterWebSocketWriteHandlers(boolean)

    • subProtocol

      public String subProtocol()
      Returns the WebSocket sub protocol selected by the WebSocket handshake.

      On the server, the value will be null when the handler receives the WebSocket callback as the handshake will not be completed yet.

      Specified by:
      subProtocol in interface WebSocketBase

    • closeStatusCode

      public Short closeStatusCode()
      Returns the close status code received from the remote endpoint or null when not yet received.
      Specified by:
      closeStatusCode in interface WebSocketBase

    • closeReason

      public String closeReason()
      Returns the close reason message from the remote endpoint or null when not yet received.
      Specified by:
      closeReason in interface WebSocketBase

    • headers

      public io.vertx.core.MultiMap headers()
      Returns the HTTP headers.
      Specified by:
      headers in interface WebSocketBase
      Returns:
      the headers

    • closeHandler

      public WebSocketBase.WebSocketBaseImpl closeHandler(Runnable handler)
      Set a close handler. This will be called when the WebSocket is closed.

      After this callback, no more messages are expected. When the WebSocket received a close frame, the closeStatusCode() will return the status code and closeReason() will return the reason.

      Specified by:
      closeHandler in interface WebSocketBase
      Parameters:
      handler - the handler. Can be null.
      Returns:
      a reference to this, so the API can be used fluently

    • shutdownHandler

      public WebSocketBase.WebSocketBaseImpl shutdownHandler(Runnable handler)
      Set a handler notified when the WebSocket is shutdown: the client or server will close the connection within a certain amount of time. This gives the opportunity to the handler to close the WebSocket gracefully before the WebSocket is forcefully closed.
      Specified by:
      shutdownHandler in interface WebSocketBase
      Parameters:
      handler - the handler notified with the remaining shutdown. Can be null.
      Returns:
      a reference to this, so the API can be used fluently

    • frameHandler

      public WebSocketBase.WebSocketBaseImpl frameHandler(Consumer<io.vertx.core.http.WebSocketFrame> handler)
      Set a frame handler on the connection. This handler will be called when frames are read on the connection.
      Specified by:
      frameHandler in interface WebSocketBase
      Parameters:
      handler - the handler. Can be null.
      Returns:
      a reference to this, so the API can be used fluently

    • textMessageHandler

      public WebSocketBase.WebSocketBaseImpl textMessageHandler(Consumer<String> handler)
      Set a text message handler on the connection. This handler will be called similar to the #binaryMessageHandler(Handler), but the buffer will be converted to a String first
      Specified by:
      textMessageHandler in interface WebSocketBase
      Parameters:
      handler - the handler. Can be null.
      Returns:
      a reference to this, so the API can be used fluently

    • binaryMessageHandler

      public WebSocketBase.WebSocketBaseImpl binaryMessageHandler(Consumer<io.vertx.core.buffer.Buffer> handler)
      Set a binary message handler on the connection. This handler serves a similar purpose to #handler(Handler) except that if a message comes into the socket in multiple frames, the data from the frames will be aggregated into a single buffer before calling the handler (using WebSocketFrame.isFinal() to find the boundaries).
      Specified by:
      binaryMessageHandler in interface WebSocketBase
      Parameters:
      handler - the handler. Can be null.
      Returns:
      a reference to this, so the API can be used fluently

    • pongHandler

      public WebSocketBase.WebSocketBaseImpl pongHandler(Consumer<io.vertx.core.buffer.Buffer> handler)
      Set a pong frame handler on the connection. This handler will be invoked every time a pong frame is received on the server, and can be used by both clients and servers since the RFC 6455 section 5.5.2 and section 5.5.3 do not specify whether the client or server sends a ping.

      Pong frames may be at most 125 bytes (octets).

      There is no ping handler since ping frames should immediately be responded to with a pong frame with identical content

      Pong frames may be received unsolicited.

      Specified by:
      pongHandler in interface WebSocketBase
      Parameters:
      handler - the handler. Can be null.
      Returns:
      a reference to this, so the API can be used fluently

    • remoteAddress

      public io.vertx.core.net.SocketAddress remoteAddress()
      Specified by:
      remoteAddress in interface WebSocketBase
      Returns:
      the remote address for this connection, possibly null (e.g a server bound on a domain socket). If useProxyProtocol is set to true, the address returned will be of the actual connecting client.

    • localAddress

      public io.vertx.core.net.SocketAddress localAddress()
      Specified by:
      localAddress in interface WebSocketBase
      Returns:
      the local address for this connection, possibly null (e.g a server bound on a domain socket) If useProxyProtocol is set to true, the address returned will be of the proxy.

    • isSsl

      public boolean isSsl()
      Specified by:
      isSsl in interface WebSocketBase
      Returns:
      true if this HttpConnection is encrypted via SSL/TLS.

    • isClosed

      public boolean isClosed()
      Specified by:
      isClosed in interface WebSocketBase
      Returns:
      true if the WebSocket cannot be used to send message anymore

    • sslSession

      public SSLSession sslSession()
      Specified by:
      sslSession in interface WebSocketBase
      Returns:
      SSLSession associated with the underlying socket. Returns null if connection is not SSL.
      See Also:

    • pipe

      public Pipe<io.vertx.core.buffer.Buffer> pipe()
      Pause this stream and return a Pipe to transfer the elements of this stream to a destination WriteStream.

      The stream will be resumed when the pipe will be wired to a WriteStream.

      Specified by:
      pipe in interface ReadStream<io.vertx.core.buffer.Buffer>
      Specified by:
      pipe in interface WebSocketBase
      Returns:
      a pipe

    • writeQueueFull

      public boolean writeQueueFull()
      This will return true if there are more bytes in the write queue than the value set using setWriteQueueMaxSize(int)
      Specified by:
      writeQueueFull in interface WebSocketBase
      Specified by:
      writeQueueFull in interface WriteStream<io.vertx.core.buffer.Buffer>
      Returns:
      true if write queue is full

    • toMulti

      @CheckReturnValue public io.smallrye.mutiny.Multi<io.vertx.core.buffer.Buffer> toMulti()
      Specified by:
      toMulti in interface WebSocketBase

    • toBlockingIterable

      public Iterable<io.vertx.core.buffer.Buffer> toBlockingIterable()

    • toBlockingStream

      public Stream<io.vertx.core.buffer.Buffer> toBlockingStream()