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
With long-polling transport, and MessageLengthInterceptor, whenever two messages arrive in a single request, they are split along the delimiter, but the onMessage callback is called only for the last one.
For example, raw message is a string '{"message1" : null}|{"message2" : null}|'
Only a single onMessage(respose) is called, with response.responseBody containing '{"message2" : null}';
The text was updated successfully, but these errors were encountered:
Same problem. This is more easily reproducible if HeaderBroadcasterCache is added.
_invokeCallback is executed with 're-opening' state before 'messageReceived' state. _response.responseBody will be overwritten by last splitted message during 're-opening' state
With long-polling transport, and MessageLengthInterceptor, whenever two messages arrive in a single request, they are split along the delimiter, but the onMessage callback is called only for the last one.
For example, raw message is a string '{"message1" : null}|{"message2" : null}|'
Only a single onMessage(respose) is called, with response.responseBody containing '{"message2" : null}';
The text was updated successfully, but these errors were encountered: