Hi Tomasz, Thanks for the response. I am referring to following scenario. 1. User A is running xmpp client at his iPHONE 2. User B is running xmpp client at his desktop 3. User B sends message to A, but A's xmpp client is either not running or running in background. 4. Server stores the message for later delivery. 5. Server informs A by sending a message using apple push notification infrastructure. 6. User A accepts the push and A's xmpp client connects to server and server delivery the message to A.
I was thinking following. 1. Develop a "pns" (Push notification system) component. 2. "pns" connects to router. 3. "c2s" (mod_status) duplicates the incoming "presence" (both available & unavailable) to "pns". 4. "c2s" (mod_deliver) duplicates the message scheduled for storage to "pns". 5. "pns" connects to apple notification system and sends the message. What your opinion here? Do I have something where I can refer this flow. / On Thu, Jan 9, 2014 at 2:49 PM, Tomasz Sterna <[email protected]> wrote: > Dnia 2014-01-09, czw o godzinie 09:07 +0530, Kumar Deepak pisze: > > > I was thinking to integrate push notification system to inform about > > incoming messages for xmpp clients. Clearly, the case comes when > > clients become unavailable on mobile client. > > I don't quite clearly understand what you need. > > IIRC you would like a method to notify a disconnected client, that there > are pending offline messages waiting and it needs to connect to get > these; > am I right? > > > > -- > Tomasz Sterna @ http://abadcafe.pl/ @ http://www.xiaoka.com/ > > > >
