On Jun 27, 2006, at 4:09 AM, Bruce Campbell wrote:
Well, not really. You'll get a TCP ack back, which should be enough to keep the lights on.Not if you are dealing with inspection-type firewalls which don't really treat a TCP ACK as a data packet.
If firewalls did this, TCP would *break* for all applications. Can you please give a concrete example of a firewall that has this property?
I guess the point I'm trying to make is, do you want the clients to know that their next <message/> will not generate a TCP error, or do you want clients to know that their next <message/>, if not delivered, will come back with an undeliverable stanza ?
You never know this, no matter how many pings you send of whatever type. What we're trying to do is detect as soon as possible that the connection has been dropped, in the case of a hard machine crash on the other side or a network cable being pulled.
smime.p7s
Description: S/MIME cryptographic signature
