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
When message is too big, the message is lost. Currently there is no other alternative.
Expected behavior
When message is too big, the message is split by the worker/platform into chunks. The client receives chunks and recompose the whole message and then trigger the promise with the full message.
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Just why ZetaPush imposes to use CometD for exchanges AND limits size of messages ?
If I have one exchange protocol, why couldn't be able to do anything I want with it ?
Please tell us about your environment:
Operating System:
Node Version: any
Npm Version: any
@angular/* Version: any
The text was updated successfully, but these errors were encountered:
I'm submitting a ... (check one with "x")
Scope (check one with "x")
Current behavior
When message is too big, the message is lost. Currently there is no other alternative.
Expected behavior
When message is too big, the message is split by the worker/platform into chunks. The client receives chunks and recompose the whole message and then trigger the promise with the full message.
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Just why ZetaPush imposes to use CometD for exchanges AND limits size of messages ?
If I have one exchange protocol, why couldn't be able to do anything I want with it ?
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: