You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 5, 2018. It is now read-only.
Sometimes the size of a message gets bigger than the maxTextMessageBufferSize of the underlying websocket. On the server, we use MessageHandler.Partial<String> for received messages, but we haven't had a look at sent message so far.
We could use the analogous RemoteEndpoint.Basic.sendText(String, boolean) but that requires synchronized communication. If you mix it with asynchronous communication RemoteEndpoint.Async.sendText(String) you have to be prepared to get IllegalStateExceptions in case they overlap. If we stick to synchronous sending, we might hit performance issues.
The simplest solution seems to be to increase the buffer size, but that's not very universal.
Maybe there are better options?
The text was updated successfully, but these errors were encountered:
Sometimes the size of a message gets bigger than the
maxTextMessageBufferSize
of the underlying websocket. On the server, we useMessageHandler.Partial<String>
for received messages, but we haven't had a look at sent message so far.We could use the analogous
RemoteEndpoint.Basic.sendText(String, boolean)
but that requires synchronized communication. If you mix it with asynchronous communicationRemoteEndpoint.Async.sendText(String)
you have to be prepared to getIllegalStateExceptions
in case they overlap. If we stick to synchronous sending, we might hit performance issues.The simplest solution seems to be to increase the buffer size, but that's not very universal.
Maybe there are better options?
The text was updated successfully, but these errors were encountered: