2 ms·
Though as described here: http://op-co.de/blog/posts/mobile_xmpp_in_2014/#index2h2 http://op-co.de/blog/posts/mobile_xmpp_in_2014/#index2h2 -- Message Carbons d
by schneid 13y ago
Though as described here: http://op-co.de/blog/posts/mobile_xmpp_in_2014/#index2h2 http://op-co.de/blog/posts/mobile_xmpp_in_2014/#index2h2 -- Message Carbons don't help if your phone is out of coverage for a few minutes, as your desktop client will get the carbons, but when you come back online, you'll be oblivious to any messages sent during that time.
- imaginator 13y agoGe0rg wrote that post shortly before the last XMPP summit. Then we put together the plans for push notifications (https://github.com/legastero/customxeps/blob/gh-pages/extensions/push.md https://github.com/legastero/customxeps/blob/gh-pages/extens...) working in conjunction with Message archive management (http://xmpp.org/extensions/xep-0313.html http://xmpp.org/extensions/xep-0313.html) to catch up on messages that might have been missed (in your example: on your desktop client).
- schneid 13y agoCool, thanks for the link. I knew about MAM, but hadn't seen the push stuff.
- imaginator 13y agoBe aware that push is very early. But there are two working implementations already - oTalk and Buddycloud (https://github.com/buddycloud/buddycloud-pusher https://github.com/buddycloud/buddycloud-pusher). What's interesting is that we both came up with very similar solutions. So specing something official and then adapting our code to match the spec should be trivial (in the grand scheme of things).