[jdev] Roster caching

[Peter Saint-Andre]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm not sure what your post has to do with roster caching, but...

Norman Rasmussen wrote:

> how do you sync your rosters?  Typically transports are used to
> connect to *legacy* networks.  Some of these have the concept of
> 'groups', so JEP's like 0144 (Roster Item Exchange - rosterx) were
> created.
> 
> As it happens the JEP only gives examples of legacy --> xmpp contact
> information.  It doesn't explicitly cater for communicating the group
> changes *back* to the transport.
> 
> So for example if someone registers with a transport (msn,aim,icq,
> afaik yahoo is the only one that implements rosterx), and gets their
> groups via rosterx (if they're lucky that their client support is) -
> the group information only flows: legacy --> xmpp.  If they change the
> group the contact is a member of, then the legacy network doesn't here
> about it.  (Should it? - that's surely up to the user to decide, but
> atm we can't tell the legacy network in any way).
> 
> This becomes more obvious with the jabber-transport, xmpp-transport,
> hatrack (what ever you want to call it), because there are xmpp
> semantics on _both_ sides.
> 
> Now obviously rosterx could be extended to handle group information
> flow back to the transport 

Is an extension even needed? As far as I can see, the group info can
flow both ways. There are no examples of that in JEP-0144, but examples
can always be added.

Peter

- --
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEWnxRNF1RSzyt3NURAmFtAJ9Y4T3US30oqq8K6Itn8A1I+wPGeQCfQUEG
BPz3IrntUkvdrFqw4fq/ZxE=
=aMzF
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://www.jabber.org/jdev/attachments/20060504/a7332192/attachment-0002.bin>