Implementations of this interface are encouraged to handle exceptions locally where
it makes sense or alternatively let the exception bubble up in which case by default
the exception is logged and the session closed with
SERVER_ERROR(1011). The exception handling
strategy is provided by
ExceptionWebSocketHandlerDecorator and it can be customized or replaced by decorating
the WebSocketHandler with a different decorator.

afterConnectionClosed

Invoked after the WebSocket connection has been closed by either side, or after a
transport error has occurred. Although the session may technically still be open,
depending on the underlying implementation, sending messages at this point is
discouraged and most likely will not succeed.

Throws:

Exception - this method can handle or propagate exceptions; see class-level
Javadoc for details.

supportsPartialMessages

boolean supportsPartialMessages()

Whether the WebSocketHandler handles partial messages. If this flag is set to
true and the underlying WebSocket server supports partial messages,
then a large WebSocket message, or one of an unknown size may be split and
maybe received over multiple calls to
handleMessage(WebSocketSession, WebSocketMessage). The flag
WebSocketMessage.isLast() indicates if
the message is partial and whether it is the last part.