I'd like to note that HipChat has planned an implementation of this spec (and, in fact, already uses an earlier version of the spec under our own namespace). Once it's accepted I'll swap the namespace over to the one in the spec and implement the remaining parts that we use our HTTP API for in XMPP as well.
I've also had some interest from a client dev for implementing this to cache capabilities / features. —Sam On Fri, Oct 2, 2015 at 10:47 AM, XMPP Extensions Editor <[email protected]> wrote: > The XMPP Extensions Editor has received a proposal for a new XEP. > > Title: Entity Versioning > > Abstract: > A method by which lists of items may be versioned so that servers will not > need to send the entire list if it has not been modified, saving bandwidth > and time with minimal state being stored by the server and client. > > > URL: http://xmpp.org/extensions/inbox/entityversioning.html > > The XMPP Council will decide in the next two weeks whether to accept this > proposal as an official XEP. > -- Sam Whited pub 4096R/54083AE104EA7AD3 https://blog.samwhited.com
