On 04/01/2010 06:53 PM, Dave Cridland wrote:
Heh - I might have known the only other ACAP user in existence would
have suggested it too.
:)
BTW, I think a roaming mechanism should not only use Pubsub storage
but also XEP-0247: Jingle XML Streams or XEP-0265: Out-of-Band
Stream Data for large datasets synchronization to bypass traffic
shaping.
Perhaps there could be a XEP for XMPP sync which would combine
Pubsub and Jingle, though.
I'd hope that individual data items could be discrete, so could flow
easily through the XMPP session, and only flow as required.
Actually I think Pubsub should be used for discrete modifications (e.g.
: user modifies some parameters or add a new search engine to her
browser) and Jingle for large datasets (e.g. : initial sync).
Thinking also that a hash could be included in each sync stanza by the
server so that clients could determine if they're up-to-date.
Wondering how Google bookmarks sync work. Has someone logged XMPP sync
traffic on Chrome ? Does it use Jingle ?
After all, if ACAP could do this in 1997, I'd assume that XMPP could
do it better now...
Yeah, I agree, it's time you write a XEP for XMPP sync. ;)
--
kael
_______________________________________________
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: [email protected]
_______________________________________________
