-
Notifications
You must be signed in to change notification settings - Fork 201
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
Push status inquiry #35
Comments
Until now, no, we do not have such support. However, I do think it is a very important feature and should be added in recent release. May I know something more about your requirement? like which kind of status do you want to know? Total number of services? Total number of subscribers under some service? Another obstacle we have here is redis. Well.. Redis is a wonderful datastore. However, not as powerful as we need right now. To support more complicated queries for status, we may need a relational database. This is partly why I did not start on the feature of status checking --- I think I may need to support SQL databases first, then add some other complex queries on top of the relational databases. I will consider this feature request carefully and come up with some applicable approach. |
umm.. sorry, actually i would like to have a delivery status of each push request, which i can inquiry by webservice. As i am thinking if the push request is failed in first time, then it should be retry in the background. right? but the service has already returned the failed message to my http client. then how can I get the successful message if it really send successful? Besides, i found that, maybe i'm wrong, it seems hasn't save the push request into datastore, which i'm thinking if the service down suddenly while the message is pushing. Could it be resume to which subscriber i'm sending to? Btw, the uniqush is great pushing system, it helps me a lot. |
Thanks for using uniqush! To answer your questions:
With that being said, you may have a question like How can I make sure that the device has received my message? A short answer is: You can't. Because neither GCM, nor APNS can guarantee the success of delivery. But remember, this is not the end of the world. Uniqush (as a system) provides (or will provide) another program to solve this problem. To understand the solution, you need to remember: Uniqush is a name of a system that providing communication facility for mobile apps. uniqush-push is only one program. It is a part of Uniqush system, but not the only part. There are other parts, like uniqush-conn, and some other client libraries. uniqush-conn provides a facility so that mobile devices can establish TCP connections with server side to retrieve/send message from/to the server. Some typical use case is like this: Server sends a message to uniqush-conn, saying it wants to send the message to some client; Then uniqush-conn will store the message in some datastore (redis, mysql, postgresql, etc.). If there is a TCP connection between uniqush-conn and the client, uniqush-conn will send the message directly through this connection; otherwise, uniqush-conn will ask uniqush-push to push some notification to the client, including a message ID. Once the client received the push notification, it will then connect to uniqush-conn and ask for that message with its message ID. Then the problem here is: What if uniqush-push cannot send the message? What if the notification got lost? uniqush-conn provides a function that allows client to request messages sent between a time interval. As I mentioned before, uniqush-conn stores the message in a datastore. The client can connect with uniqush-conn saying I need all messages sent on yesterday. Then uniqush-conn will retrieve those messages from the datastore and send them to the client. |
Can uniqush-push has webservice for inquiring the status by service and each of subscriber
The text was updated successfully, but these errors were encountered: