Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split big messages in chunks #71

Open
aurelien-baudet opened this issue Jul 5, 2018 · 0 comments
Open

Split big messages in chunks #71

aurelien-baudet opened this issue Jul 5, 2018 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@aurelien-baudet
Copy link
Contributor

I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[X] feature request

Scope (check one with "x")

[ ] @zetapush/cli
[X] @zetapush/cometd
[ ] @zetapush/core
[ ] @zetapush/create
[ ] @zetapush/platform
[ ] @zetapush/worker

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:

  • Operating System:
  • Node Version: any
  • Npm Version: any
  • @angular/* Version: any
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants