[jdev] XMPP Ping/Keepalive: Recommended method ?

[Joe Hildebrand]

Ah, I misunderstood what your negative was about.  I thought you were  
saying that the ACKs don't make it back. :)

On Jun 28, 2006, at 3:04 AM, Bruce Campbell wrote:

> On Tue, 27 Jun 2006, Joe Hildebrand wrote:
>
>> Date: Tue, 27 Jun 2006 05:59:54 -0600
>> From: Joe Hildebrand <hildjj at gmail.com>
>> Reply-To: Jabber software development list <jdev at jabber.org>
>> To: Jabber software development list <jdev at jabber.org>
>> Subject: Re: [jdev] XMPP Ping/Keepalive: Recommended method ?
>> 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?
>
> Not a firewall appliance, but 'interesting' configurations with  
> ISPs seeking to keep their dial-up lines/wavelan channels free  
> (timers on their end were only reset on certain types of packets,  
> which did not include tcp acks).
>
> -- 
>   Bruce Campbell

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1883 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20060701/381f162e/attachment-0002.bin>