-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/15/09 9:12 AM, Jiří Zárevúcky wrote:
> We probably first need to sum up the additional functionality we'd > want in roster management. > Arbitrary attached XML is the first and obvious one, which wouldn't > even require a new protocol. Correct! The "X" in XMPP stands for "extensible". :) So maybe we need a service discovery feature for roster extensions and away we go. No need for a redesign of jabber:iq:roster at that point! > Are there any other functionalities we may want? Perhaps some more > sophisticated handling including JID and group filtering, etc. I think > I saw something about some "roster activation" here. What was that > about? The requirements for such features are quite nebulous, IMHO. If someone cares about them, they can work to define them more clearly. At the moment I don't feel there are any truly compelling use cases here, but I freely admit that I might be wrong because I haven't thought about it in detail yet. The "roster activation" idea is an optimization for mobile environments that we talked about at XMPP Summit 6 earlier this year. Refer to the list archives for a bit more insight into what that might mean. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpd8zAACgkQNL8k5A2w/vy1HwCggxf5+oi/g2sg7Sfx/2UG4Y60 lFEAn1R3iuJs2iWo5gd4w//qbiPZEzkn =niYQ -----END PGP SIGNATURE-----
