[Standards-JIG] What happened to the ACK proposal?

Maciek Niedzielski machekku at miroku.uaznia.net
Mon Aug 15 18:30:47 UTC 2005

Hash: SHA1

Peter Saint-Andre wrote:
> David Chisnall wrote:
>> The problem is not with Java, it is with TCP.  
> That's one reason the ACK proposal was not accepted as a JEP:
> http://mail.jabber.org/pipermail/standards-jig/2005-March/007174.html

Ok, so the point is that good TCP implementation should be able to
notify the sender that the message could not be delivered.
But the question now is: what does it really mean that the message was
delivered and is it possible for the transport layer to really know
about it?

Have you ever been is such situation: you're logging out from the
system, and in the very last moment, when everything is shutting down,
your jabber client tells you: "you just got a message and it says....."
and it's too late to read it. Was the message delivered?
If you're lucky, it's saved in the history. But the sender will assume
that you could read it, because they got no error.
And if you're unlucky, you will never be able to read this message,
because you were chatting at internet cafe or any other place where you
cannot or don't want to save history. Was the message really delivered?

- --
 xmpp:machekku at chrome.pl
Version: GnuPG v1.2.1-nr1 (Windows XP)


More information about the Standards mailing list