On 3/31/09 6:07 AM, Fabio Forno wrote: > On Tue, Mar 31, 2009 at 3:23 AM, XMPP Extensions Editor <edi...@xmpp.org> > wrote: >> Version 0.7 of XEP-0198 (Stream Management) has been released. >> >> Abstract: This specification defines an XMPP protocol extension for active >> management of an XML stream between two XMPP entities, including features >> for stanza acknowledgements and stream resumption. >> >> Changelog: Removed pings (use XEP-0199, whitespace pings, or TCP keepalives >> instead); removed section on throttling, since it is unworkable. (jjh/psa) > > Imho some throttling "notification" is feasible only in one way: it's > up to the server send unsolicited throttling notifications when it > knows it is throttling voluntary the stream (this means that if > packets are stuck in a TCP buffer it's likely that even the server > doesn't know that the stream is being throttled). Anything triggered > by a stanza sent by the client is unworkable since that stanza cannot > have higher priority and pass ahead the others. > As optional I'd put a stanza for this purpose: > > S: <t xmlns='urn:xmpp:sm:1' max="n"/> > > It isn't perfect but it can work for most of the cases.
Agreed. But what is the purpose of max="n" here? Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
