|
Hello,
I have noticed that WinJab, Exodus, and JIM all send a bit of whitespace to
the server once a minute.
In my own client, which uses JabberCOM, I noticed that I can't leave the
client connected overnight... When I get in the next day, it appears that the
connection has ended, though JabberCOM doesn't seem to know it (the
OnDisconnected event never gets fired)... It's as if the server is
abandoning the connection without telling the client (pehaps because it thinks
the client isn't there anymore).
Does the server need to see a bit of activity from the client regularly in
order for the connection to stay alive? The behavior in WinJab, Exodus,
and JIM seem to indicate this. Should my client emulate their behavior
(i.e. sending "<sp><tab><sp>" every 60 seconds)?
Thanks.
--sk!
|
- Re: [JDEV] client timeouts Sean Kirkby
- Re: [JDEV] client timeouts Matthias Wimmer
- RE: [JDEV] client timeouts PINSON Frederique FTRD/DMI/LAN
- Re: [JDEV] client timeouts Sean Kirkby
- Re: [JDEV] client timeouts Matthias Wimmer
- Re: [JDEV] client timeouts David Waite
