-
Notifications
You must be signed in to change notification settings - Fork 205
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
Persistent connection and upstream messaging over CCS #109
Comments
This would be awesome to have added to your library. Benchmarking this for one registration id at a time I get about 300/second where apn gives me about 15000/second to iOS devices since it uses a persistent connection. I know I can bulk-send up to 1000 pushIds with your module over https, but when I personalize the messages this no longer works because the payload changes per target device. Please consider adding this. The performance gains would be incredible. |
+1 to this! |
What is the status of this feature? |
@hypesystem How hard is this to implement? Can you summarize the tasks and changes involved? I imagine this being a new API call in |
The project has not yet been started, and this would require implementing a connection to an entirely new API. In addition, it would introduce concerns that we have not even considered yet (like a persistent long-running connection, instead of discrete HTTP connections for each call). I don't have an overview of exactly what would need to happen, but it seems like a big addition 😄 If anyone has time for it, I would recommend making a new branch explicitly for developing this interface, and I would love to review everything you do. Unfortunately, however, this is not a feature that is high on my own list. |
i needed upstream messaging and tried this but then realized this is just using the http protocol. there's a node project with xmpp/upstream support: https://github.com/jacobp100/node-gcm-ccs |
CCS allows for a persistent connection between server and client. https://developers.google.com/cloud-messaging/ccs
Upstream messaging (the server receiving messages from the clients) depends on CCS, and is the primary reason for implementing this.
I expect this to be a big change to implement (hence no milestone yet).
The text was updated successfully, but these errors were encountered: