2009/7/15 Peter Saint-Andre <[email protected]>: > > 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! >
You've got a point. But let's look at this from another perspective. XMPP-IM doesn't dictate jabber:iq:roster has to be used, right? Then there is nothing wrong if a few people with a lot of free time write a purely experimental XEP defining a new way to access and manage roster. Developers who like the idea could just play with it... no obligations for anyone else. :) Well, that's the theory, anyway. The question is whether more people would be interested in such experiment. :) >> 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. I agree with that. > 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 > Yes, I will. Thanks. :)
