On Di, 2015-03-03 at 11:23 +0100, Mickaël Rémond wrote: > - Is app client really an instance of an application running on a > specific device ? > I thought at first the node what acting as a device registry, but, it > seems it does not as a node is defined as: "Each PubSub node is a > delivery target for the Push Service, which could represent multiple > devices for a single user." > So, basically, I am lost. What is acting as a Client App registry ?
In my understanding an app client is the actual app running an iOS etc. The registration process is not defined (XEP-0077 is suggested). I think the idea is that there could be a proprietary app server that has nothing to do with XMPP which does the dispatching of push notifications to the push service (in the old draft version the push service, e.g. APNS, was called proprietary push service and packets sent to it were called proprietary push notifications, this makes it clearer). It needs the token and maybe additional information (at Ubuntu push an app-id) for that. The interface between app server and xmpp server is a pubsub node. The app server creates a node on a pubsub service (could be a third instance or a part of the app server) and subscribes to it. The information required for publishing on that node (hostname, node name, maybe a secret) are sent to the client app as a registration response. Then the client app hands this information over to its xmpp server using the enable-iq stanza so the xmpp server can publish push notifications when the client app is not reachable. I think one node representing multiple client apps is only possible if all of these apps use the same push service type, e.g. all of them use app ShinyApp on iOS. Otherwise the app server which maybe only supports one push service type can't decide if a published notification is for the client it is serving. > How can I see all my client app registered for push ? How can I > manage that list ? from which side? I think each client app is responsible for its own registration.
