[Standards-JIG] Re: What happened to the ACK proposal?
ian.paterson at clientside.co.uk
Thu Aug 18 00:02:57 UTC 2005
> > It just relies on client responses.
> > Every message sent to the client is buffered until recieving
> > confirmation. Any data recieved from the client counts as a
> > confirmation and the buffer is deleted. Assuming that the
> client sends
> > <presence type="unavailable" /> and/or </stream:stream>
> every message
> > is confirmed, even on client (proper) disconnection.
> > If the c2s detects broken TCP stream (most probably after sending
> > keepalive) the buffer of unconfirmed messages is backed-up to the
> > session manager for storing in offline storage.
> And what about s2s?
The network problems described by Tijl are unlikely to affect s2s. [FYI
WPJabber also uses a special modern network API that is only available
with Linux 2.6 (or a specially patched 2.4).]
More information about the Standards