On 03.06.2015 01:48, John Williams (johnwi3) wrote:
Thanks for the clarification.
Hum,.. not sure how useful this is, since a lot of stanzas are of little long
term interest (eg: chatstates), but as you describe it seems pretty harmless.
Consider the XMPP user walks into the subway without
On 3 June 2015 at 00:48, John Williams (johnwi3) john...@cisco.com wrote:
Thanks for the clarification.
Hum,.. not sure how useful this is, since a lot of stanzas are of little
long term interest (eg: chatstates), but as you describe it seems pretty
harmless.
So as things stand, if a TCP
On 29 May 2015, at 21:00, Dave Cridland d...@cridland.net wrote:
What if, on a resumption failure, a server could include the 'h' attribute,
to mean I can't actually resume your state, but I did get all the stanzas up
until H.
I think this allows servers to hold onto this small amount of
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Nonzas (are not Stanzas)
Abstract: This specification defines the term Nonza, describing every top
level stream element that is not a Stanza.
URL: http://xmpp.org/extensions/inbox/nonza.html
The XMPP Council will decide
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Unique and stable message IDs
Abstract: This specification describes unique and stable IDs for message
stanzas.
URL: http://xmpp.org/extensions/inbox/mid.html
The XMPP Council will decide in the next two weeks whether to
Thanks Florian Dave,
I made a major misunderstanding, and this now makes good sense.
I was thinking the 'h' value in the failed stanza was the servers count of
stanzas received by the session for delivery **to** the client. That is to say
a resume using that value would require
