new WebSocketBase()
Base WebSocket implementation.
- Source:
Methods
binaryHandlerID() → {string}
When a
WebSocket is created it automatically registers an event handler with the event bus - the ID of that
handler is given by this method.
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.
- Source:
Returns:
the binary handler id
-
Type
-
string
binaryMessageHandler(handler) → {WebSocketBase}
Set a binary message handler on the connection. This handler serves a similar purpose to WebSocketBase#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).
Parameters:
| Name |
Type |
Description |
handler |
function
|
the handler |
- Source:
Returns:
a reference to this, so the API can be used fluently
-
Type
-
WebSocketBase
close(statusCode, reason, handler)
Same as but with an handler called when the operation completes
Parameters:
| Name |
Type |
Description |
statusCode |
number
|
|
reason |
string
|
|
handler |
function
|
|
- Source:
closeHandler(handler) → {WebSocketBase}
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
WebSocketBase#closeStatusCode will return the status code and WebSocketBase#closeReason will return the reason.
Parameters:
| Name |
Type |
Description |
handler |
function
|
the handler |
- Source:
Returns:
a reference to this, so the API can be used fluently
-
Type
-
WebSocketBase
closeReason() → {string}
Returns the reason message received when the WebSocket was closed by the other side, otherwise null.
- Source:
Returns:
-
Type
-
string
closeStatusCode() → {number}
Returns the status code received when the WebSocket was closed by the other side, otherwise null.
- Source:
Returns:
-
Type
-
number
drainHandler(handler) → {WebSocketBase}
Parameters:
| Name |
Type |
Description |
handler |
function
|
|
- Source:
Returns:
-
Type
-
WebSocketBase
end(handler)
Calls WebSocketBase#close
Parameters:
| Name |
Type |
Description |
handler |
function
|
|
- Source:
endHandler(endHandler) → {WebSocketBase}
Parameters:
| Name |
Type |
Description |
endHandler |
function
|
|
- Source:
Returns:
-
Type
-
WebSocketBase
exceptionHandler(handler) → {WebSocketBase}
Parameters:
| Name |
Type |
Description |
handler |
function
|
|
- Source:
Returns:
-
Type
-
WebSocketBase
fetch(amount) → {WebSocketBase}
Parameters:
| Name |
Type |
Description |
amount |
number
|
|
- Source:
Returns:
-
Type
-
WebSocketBase
frameHandler(handler) → {WebSocketBase}
Set a frame handler on the connection. This handler will be called when frames are read on the connection.
Parameters:
| Name |
Type |
Description |
handler |
function
|
the handler |
- Source:
Returns:
a reference to this, so the API can be used fluently
-
Type
-
WebSocketBase
handler(handler) → {WebSocketBase}
Parameters:
| Name |
Type |
Description |
handler |
function
|
|
- Source:
Returns:
-
Type
-
WebSocketBase
isClosed() → {boolean}
- Source:
Returns:
true if the WebSocket is closed
-
Type
-
boolean
isSsl() → {boolean}
- Source:
Returns:
true if this HttpConnection is encrypted via SSL/TLS.
-
Type
-
boolean
localAddress() → {SocketAddress}
- Source:
Returns:
the local address for this socket
-
Type
-
SocketAddress
pause() → {WebSocketBase}
- Source:
Returns:
-
Type
-
WebSocketBase
pipe() → {Pipe}
Pause this stream and return a to transfer the elements of this stream to a destination .
The stream will be resumed when the pipe will be wired to a
WriteStream.
- Source:
Returns:
a pipe
-
Type
-
Pipe
pipeTo(dst, handler)
Pipe this
ReadStream to the
WriteStream.
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 handler will be
called with the result.
Parameters:
| Name |
Type |
Description |
dst |
WriteStream
|
the destination write stream |
handler |
function
|
|
- Source:
pongHandler(handler) → {WebSocketBase}
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.
Parameters:
| Name |
Type |
Description |
handler |
function
|
the handler |
- Source:
Returns:
a reference to this, so the API can be used fluently
-
Type
-
WebSocketBase
remoteAddress() → {SocketAddress}
- Source:
Returns:
the remote address for this socket
-
Type
-
SocketAddress
resume() → {WebSocketBase}
- Source:
Returns:
-
Type
-
WebSocketBase
setWriteQueueMaxSize(maxSize) → {WebSocketBase}
Parameters:
| Name |
Type |
Description |
maxSize |
number
|
|
- Source:
Returns:
-
Type
-
WebSocketBase
subProtocol() → {string}
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.
- Source:
Returns:
-
Type
-
string
textHandlerID() → {string}
When a
WebSocket is created it automatically registers an event handler with the eventbus, the ID of that
handler is given by
textHandlerID.
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.
- Source:
Returns:
-
Type
-
string
textMessageHandler(handler) → {WebSocketBase}
Set a text message handler on the connection. This handler will be called similar to the
, but the buffer will be converted to a String first
Parameters:
| Name |
Type |
Description |
handler |
function
|
the handler |
- Source:
Returns:
a reference to this, so the API can be used fluently
-
Type
-
WebSocketBase
write(data, handler)
Same as but with an handler called when the operation completes
Parameters:
| Name |
Type |
Description |
data |
Buffer
|
|
handler |
function
|
|
- Source:
writeBinaryMessage(data, handler) → {WebSocketBase}
Same as WebSocketBase#writeBinaryMessage but with an handler called when the operation completes
Parameters:
| Name |
Type |
Description |
data |
Buffer
|
|
handler |
function
|
|
- Source:
Returns:
-
Type
-
WebSocketBase
writeFinalBinaryFrame(data, handler) → {WebSocketBase}
Same as WebSocketBase#writeFinalBinaryFrame but with an handler called when the operation completes
Parameters:
| Name |
Type |
Description |
data |
Buffer
|
|
handler |
function
|
|
- Source:
Returns:
-
Type
-
WebSocketBase
writeFinalTextFrame(text, handler) → {WebSocketBase}
Same as WebSocketBase#writeFinalTextFrame but with an handler called when the operation completes
Parameters:
| Name |
Type |
Description |
text |
string
|
|
handler |
function
|
|
- Source:
Returns:
-
Type
-
WebSocketBase
writeFrame(frame, handler) → {WebSocketBase}
Same as WebSocketBase#writeFrame but with an handler called when the operation completes
Parameters:
| Name |
Type |
Description |
frame |
WebSocketFrame
|
|
handler |
function
|
|
- Source:
Returns:
-
Type
-
WebSocketBase
writePing(data) → {WebSocketBase}
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.
Parameters:
| Name |
Type |
Description |
data |
Buffer
|
the data to write, may be at most 125 bytes |
- Source:
Returns:
a future completed with the result
-
Type
-
WebSocketBase
writePong(data) → {WebSocketBase}
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.
Parameters:
| Name |
Type |
Description |
data |
Buffer
|
the data to write, may be at most 125 bytes |
- Source:
Returns:
a reference to this, so the API can be used fluently
-
Type
-
WebSocketBase
writeQueueFull() → {boolean}
This will return true if there are more bytes in the write queue than the value set using WebSocketBase#setWriteQueueMaxSize
- Source:
Returns:
true if write queue is full
-
Type
-
boolean
writeTextMessage(text, handler) → {WebSocketBase}
Same as WebSocketBase#writeTextMessage but with an handler called when the operation completes
Parameters:
| Name |
Type |
Description |
text |
string
|
|
handler |
function
|
|
- Source:
Returns:
-
Type
-
WebSocketBase