| Modifier and Type | Method and Description |
|---|---|
| public WebSocket | |
| public WebSocket | |
| public WebSocket | |
| public WebSocket | exceptionHandler(Handler<Throwable> handler)
Redeclares io.
|
| public WebSocket | fetch(long amount)
Redeclares io. Fetch the specified |
| public WebSocket | |
| public WebSocket | |
| public WebSocket | pause()
Redeclares io. Pause the |
| public WebSocket | resume()
Redeclares io. Resume reading, and sets the buffer in |
| public WebSocket | setWriteQueueMaxSize(int
the max size of the write stream maxSize)Redeclares io. Set the maximum size of the write queue to |
| public WebSocket | writeBinaryMessage(Buffer data, Handler<AsyncResult<Void>> handler)
Redeclares io.
References Deprecated
Buffer is deprecated or references (maybe indirectly) at least one deprecated element.
Same as |
| public WebSocket | writeFinalBinaryFrame(Buffer data, Handler<AsyncResult<Void>> handler)
Redeclares io.
References Deprecated
Buffer is deprecated or references (maybe indirectly) at least one deprecated element.
Same as |
| public WebSocket | writeFinalTextFrame(String text, Handler<AsyncResult<Void>> handler)
Redeclares io. Same as |
| public WebSocket | writeFrame(WebSocketFrame frame, Handler<AsyncResult<Void>> handler)
Redeclares io. Same as |
| public WebSocket | writePing(Buffer
the data to write, may be at most 125 bytes data, Handler<AsyncResult<Void>> called when the ping frame has been successfully written handler)Redeclares io.
References Deprecated
Buffer is deprecated or references (maybe indirectly) at least one deprecated element.
Writes a ping frame to the connection. |
| public WebSocket | writePong(Buffer
the data to write, may be at most 125 bytes data, Handler<AsyncResult<Void>> called when the pong frame has been successfully written handler)Redeclares io.
References Deprecated
Buffer is deprecated or references (maybe indirectly) at least one deprecated element.
Writes a pong frame to the connection. |
| public WebSocket | writeTextMessage(String text, Handler<AsyncResult<Void>> handler)
Redeclares io. Same as |
| closeHandler | back to summary |
|---|---|
public WebSocket closeHandler(Handler<Void> handler)
| |
| drainHandler | back to summary |
|---|---|
| public WebSocket drainHandler(Handler<Void> handler) Redeclares io.
| |
| endHandler | back to summary |
|---|---|
| public WebSocket endHandler(Handler<Void> endHandler) Redeclares io.
| |
| exceptionHandler | back to summary |
|---|---|
| public WebSocket exceptionHandler(Handler<Throwable> handler) Redeclares io.
| |
| fetch | back to summary |
|---|---|
| public WebSocket fetch(long amount) Redeclares io. Doc from io. Fetch the specified | |
| frameHandler | back to summary |
|---|---|
public WebSocket frameHandler(Handler<WebSocketFrame> handler)
| |
| handler | back to summary |
|---|---|
| public WebSocket handler(Handler<Buffer> handler) Redeclares io.
| |
| pause | back to summary |
|---|---|
| public WebSocket pause() Redeclares io. Doc from io. Pause the
While it's paused, no data will be sent to the data | |
| resume | back to summary |
|---|---|
| public WebSocket resume() Redeclares io. Doc from io. Resume reading, and sets the buffer in
If the | |
| setWriteQueueMaxSize | back to summary |
|---|---|
| public WebSocket setWriteQueueMaxSize(int maxSize) Redeclares io. Doc from io. Set the maximum size of the write queue to
The value is defined by the implementation of the stream, e.g in bytes for a
| |
| writeBinaryMessage | back to summary |
|---|---|
| public WebSocket writeBinaryMessage(Buffer data, Handler<AsyncResult<Void>> handler) Redeclares io. Doc from io. References Deprecated
See corresponding docs for further information. Same as
| |
| writeFinalBinaryFrame | back to summary |
|---|---|
| public WebSocket writeFinalBinaryFrame(Buffer data, Handler<AsyncResult<Void>> handler) Redeclares io. Doc from io. References Deprecated
See corresponding docs for further information. Same as
| |
| writeFinalTextFrame | back to summary |
|---|---|
| public WebSocket writeFinalTextFrame(String text, Handler<AsyncResult<Void>> handler) Redeclares io. Doc from io. Same as
| |
| writeFrame | back to summary |
|---|---|
| public WebSocket writeFrame(WebSocketFrame frame, Handler<AsyncResult<Void>> handler) Redeclares io. Doc from io. Same as
| |
| writePing | back to summary |
|---|---|
| public WebSocket writePing(Buffer data, Handler<AsyncResult<Void>> handler) Redeclares io. Doc from io. References Deprecated
See corresponding docs for further information. 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. | |
| writePong | back to summary |
|---|---|
| public WebSocket writePong(Buffer data, Handler<AsyncResult<Void>> handler) Redeclares io. Doc from io. References Deprecated
See corresponding docs for further information. 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. | |
| writeTextMessage | back to summary |
|---|---|
| public WebSocket writeTextMessage(String text, Handler<AsyncResult<Void>> handler) Redeclares io. Doc from io. Same as
| |