Looks like Session.getMaxMessageSize() has been removed in favor of ..
Session.getMaxBinaryMessageBufferSize()
Session.getMaxTextMessageBufferSize()
Is is expected that if messages arrive exceeding those buffer sizes the
implementation fails the websocket and reports the error to the websocket?
I would think a close reason of CloseCode.TOO_BIG (1009) and indicate that
to the client.
Is this the behavior now?
--
Joakim Erdfelt <joakim_at_intalio.com>
webtide.com <http://www.webtide.com/>
Developer advice, services and support
from the Jetty & CometD experts
eclipse.org/jetty - cometd.org