On Tuesday 31 March 2009 12:45:22 Fabio Forno wrote: > On Tue, Mar 31, 2009 at 6:31 PM, Dave Cridland <d...@cridland.net> wrote: > >> Just realized: the max number of unacked stanzas could be used in > >> order to prevent throttling and negotiate the rate with server... > > > > That sounds curiously interesting. > > The present spec already does some rate limitation, since any client > supporting sm could send stanzas as fast as possible and the server > just needs to delay the acks. With a large window between acks we can > allow small bursts before starting throttling. > > Therefore I think that the throttling <t/> packet is no more needed, > unless we want to enlarge or restrict the window (but I think that > reinventing TCP goes beyond the scope of XMPP;) )
I think we still want the <t/> element so that the client knows the difference between throttling and a dead connection. Right now, clients will use XEP-199 to ping the server, and will disconnect if the server doesn't reply in time. This completely conflicts with throttling. The <t/> element solves this nicely. All clients have to do is reset their timeout anytime they receive it. And servers would need to send it regularly during throttling (say, every 30 seconds). -Justin
