On Jan 23, 2008, at 4:21 PM, Yann Leboulanger wrote:
Tomasz Sterna a écrit :
On Śr, 2008-01-23 at 17:12 +0100, Yann Leboulanger wrote:
So is it really possible to find reasonable values for all those
parameters that I don't know what they really do?
Is it tunable from python for a particular socket or is it in OS
directly?
Why do you want to tune it?
Because currently if I unplug my internet cable, my client detect
connectut after several minutes, and I'd like it to detect it faster.
But thats a problem with the OS.
If a OS looses the interface where the TCP connection is bound, it
should signal the applications that those TCP connections are no
longer valid, right?
FYI, the last time I discussed Pings on a client context scenario, we
decided on:
* whitespace pings each 45 seconds (to keep NATs happy);
* Requirement to have a XMPP ping sent if more than 45 seconds of
inactivity is detected.
The second point is worded like that because we don't immediately
send the XMPP ping. We wait 5 minutes or until the user needs it (so
the next time we send any stanza we also send the ping).
Best regards,
--
HIId: Pedro Melo
SMTP: [EMAIL PROTECTED]
XMPP: [EMAIL PROTECTED]
