Hi, Addition of this feature is highly appreciated. There is a small issue which will occur in rare scenario :
In sec 2.4, "Example 4. Roster result with no items" <iq from='ro...@montague.lit' id='r1' to='ro...@montague.lit/home' type='result'> <query xmlns='jabber:iq:roster' ver='317'> </iq> The above example is for the case when server will send the individual roster pushes for the changes rather then sending the complete roster. But the server will return the same response (while returning complete roster) when user has deleted all the rosteritems present previous version (say 316). Also a minor correction is the 'query' element in the above example is not closed. Regards, Sachin Khandelwal On Thursday 09 April 2009 01:34:40 XMPP Extensions Editor wrote: > This message constitutes notice of a Last Call for comments on XEP-0237 > (Roster Versioning). > > Abstract: This specification defines a proposed modification to the XMPP > roster protocol that enables versioning of rosters such that the server > will not send the roster to the client if the roster has not changed, thus > saving bandwidth during session establishment. > > URL: http://www.xmpp.org/extensions/xep-0237.html > > This Last Call begins today and shall end at the close of business on > 2009-04-21. > > Please consider the following questions during this Last Call and send your > feedback to the standards@xmpp.org discussion list: > > 1. Is this specification needed to fill gaps in the XMPP protocol stack or > to clarify an existing protocol? 2. Does the specification solve the > problem stated in the introduction and requirements? 3. Do you plan to > implement this specification in your code? If not, why not? 4. Do you have > any security concerns related to this specification? 5. Is the > specification accurate and clearly written? > > Your feedback is appreciated!
