Class WebSocketTransport
Transport
that uses a
WebSocketClient
.- Since:
- 4.1
- Author:
- Rossen Stoyanchev
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionconnect
(TransportRequest request, WebSocketHandler handler) Connect the transport.Return the SockJS transport types that this transport can be used for.Return the configuredWebSocketClient
.boolean
Check whether this component is currently running.void
start()
Start this component.void
stop()
Stop this component, typically in a synchronous fashion, such that the component is fully stopped upon return of this method.toString()
-
Constructor Details
-
WebSocketTransport
-
-
Method Details
-
getWebSocketClient
Return the configuredWebSocketClient
. -
getTransportTypes
Description copied from interface:Transport
Return the SockJS transport types that this transport can be used for. In particular since from a client perspective there is no difference between XHR and XHR streaming, anXhrTransport
could do both.- Specified by:
getTransportTypes
in interfaceTransport
-
connect
public ListenableFuture<WebSocketSession> connect(TransportRequest request, WebSocketHandler handler) Description copied from interface:Transport
Connect the transport. -
start
public void start()Description copied from interface:Lifecycle
Start this component.Should not throw an exception if the component is already running.
In the case of a container, this will propagate the start signal to all components that apply.
-
stop
public void stop()Description copied from interface:Lifecycle
Stop this component, typically in a synchronous fashion, such that the component is fully stopped upon return of this method. Consider implementingSmartLifecycle
and itsstop(Runnable)
variant when asynchronous stop behavior is necessary.Note that this stop notification is not guaranteed to come before destruction: On regular shutdown,
Lifecycle
beans will first receive a stop notification before the general destruction callbacks are being propagated; however, on hot refresh during a context's lifetime or on aborted refresh attempts, a given bean's destroy method will be called without any consideration of stop signals upfront.Should not throw an exception if the component is not running (not started yet).
In the case of a container, this will propagate the stop signal to all components that apply.
-
isRunning
public boolean isRunning()Description copied from interface:Lifecycle
Check whether this component is currently running.In the case of a container, this will return
true
only if all components that apply are currently running. -
toString
-