public abstract class AbstractListenerWebSocketSession<T> extends AbstractWebSocketSession<T> implements org.reactivestreams.Subscriber<Void>
WebSocketSession implementations that bridge between
event-listener WebSocket APIs (e.g. Java WebSocket API JSR-356, Jetty,
Undertow) and Reactive Streams.
Also an implementation of Subscriber<Void> so it can be used as
the completion subscriber for session handling
| Modifier and Type | Class and Description |
|---|---|
protected class |
AbstractListenerWebSocketSession.WebSocketSendProcessor |
| Constructor and Description |
|---|
AbstractListenerWebSocketSession(T delegate,
String id,
HandshakeInfo handshakeInfo,
DataBufferFactory bufferFactory)
Base constructor.
|
AbstractListenerWebSocketSession(T delegate,
String id,
HandshakeInfo handshakeInfo,
DataBufferFactory bufferFactory,
reactor.core.publisher.MonoProcessor<Void> completionMono)
Alternative constructor with completion
Mono<Void> to propagate
the session completion (success or error) (for client-side use). |
| Modifier and Type | Method and Description |
|---|---|
protected abstract boolean |
canSuspendReceiving()
Whether the underlying WebSocket API has flow control and can suspend and
resume the receiving of messages.
|
protected AbstractListenerWebSocketSession.WebSocketSendProcessor |
getSendProcessor() |
void |
onComplete() |
void |
onError(Throwable ex) |
void |
onNext(Void aVoid) |
void |
onSubscribe(org.reactivestreams.Subscription subscription) |
reactor.core.publisher.Flux<WebSocketMessage> |
receive()
Provides access to the stream of inbound messages.
|
protected abstract void |
resumeReceiving()
Resume receiving new message(s) after demand is generated by the
downstream Subscriber.
|
reactor.core.publisher.Mono<Void> |
send(org.reactivestreams.Publisher<WebSocketMessage> messages)
Give a source of outgoing messages, write the messages and return a
Mono<Void> that completes when the source completes and writing
is done. |
protected abstract boolean |
sendMessage(WebSocketMessage message)
Send the given WebSocket message.
|
protected abstract void |
suspendReceiving()
Suspend receiving until received message(s) are processed and more demand
is generated by the downstream Subscriber.
|
binaryMessage, bufferFactory, getDelegate, getHandshakeInfo, getId, pingMessage, pongMessage, textMessage, toStringclone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitclose, closepublic AbstractListenerWebSocketSession(T delegate, String id, HandshakeInfo handshakeInfo, DataBufferFactory bufferFactory)
delegate - the native WebSocket session, channel, or connectionid - the session idhandshakeInfo - the handshake infobufferFactory - the DataBuffer factor for the current connectionpublic AbstractListenerWebSocketSession(T delegate, String id, HandshakeInfo handshakeInfo, DataBufferFactory bufferFactory, @Nullable reactor.core.publisher.MonoProcessor<Void> completionMono)
Mono<Void> to propagate
the session completion (success or error) (for client-side use).protected AbstractListenerWebSocketSession.WebSocketSendProcessor getSendProcessor()
public reactor.core.publisher.Flux<WebSocketMessage> receive()
WebSocketSessionThis stream receives a completion or error signal when the connection
is closed. In a typical WebSocketHandler implementation this
stream is composed into the overall processing flow, so that when the
connection is closed, handling will end.
See the class-level doc of WebSocketHandler and the reference
for more details and examples of how to handle the session.
receive in interface WebSocketSessionreceive in class AbstractWebSocketSession<T>public reactor.core.publisher.Mono<Void> send(org.reactivestreams.Publisher<WebSocketMessage> messages)
WebSocketSessionMono<Void> that completes when the source completes and writing
is done.
See the class-level doc of WebSocketHandler and the reference
for more details and examples of how to handle the session.
send in interface WebSocketSessionsend in class AbstractWebSocketSession<T>protected abstract boolean canSuspendReceiving()
Note: Sub-classes are encouraged to start out in suspended mode, if possible, and wait until demand is received.
protected abstract void suspendReceiving()
Note: if the underlying WebSocket API does not provide
flow control for receiving messages, this method should be a no-op
and canSuspendReceiving() should return false.
protected abstract void resumeReceiving()
Note: if the underlying WebSocket API does not provide
flow control for receiving messages, this method should be a no-op
and canSuspendReceiving() should return false.
protected abstract boolean sendMessage(WebSocketMessage message) throws IOException
Note: Sub-classes are responsible for releasing the payload data buffer, once fully written, if pooled buffers apply to the underlying container.
IOExceptionpublic void onSubscribe(org.reactivestreams.Subscription subscription)
onSubscribe in interface org.reactivestreams.Subscriber<Void>public void onNext(Void aVoid)
onNext in interface org.reactivestreams.Subscriber<Void>public void onError(Throwable ex)
onError in interface org.reactivestreams.Subscriber<Void>public void onComplete()
onComplete in interface org.reactivestreams.Subscriber<Void>