[Standards-JIG] Re: WHACK

Peter Saint-Andre stpeter at jabber.org
Wed Apr 26 20:04:03 UTC 2006

Hash: SHA1

Peter Saint-Andre wrote:
> Dave Cridland wrote:
>>> On Wed Apr 26 07:55:18 2006, Jacek Konieczny wrote:
>>>>> In general, hop-by-hop reliability is only a problem in as much as
>>>> it > can be difficult to know whether the connection is still alive.
>>>> ... and when it become dead, so the application is able to tell the user
>>>> which messages could be lost. We could save some bandwith by not trying
>>>> too keep exact account of stanzas delivered to link peer, but
>>>> application should be able to detect which stanzas were delivered for
>>>> sure and which could be lost. And the number of "probably lost" stanzas
>>>> should never be too big, so there is no need to buffer too much (stanzas
>>>> sent) on application side.
>>> Exactly, hence my suggestion. Something like the client sending:
>>> <message from="foo at example.org" to="bar at example.net" ack:seq="25"/>
> Why not just this?
> <message from="foo at example.org" to="bar at example.net" id="25"/>
> We already have the 'id' attribute. Just include the sequence number in
> every stanza you generate and increment by 1 for each stanza.

Well, that won't work for all hops because the server preserves the 'id'
attribute. Never mind.


- --
Peter Saint-Andre
Jabber Software Foundation

Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060426/a5a493d0/attachment.bin>

More information about the Standards mailing list