Perhaps it's a known problem - today I wondered why one contact didn't go offline, while I knew that the computer the client ran on was disconnected from the network.
tcpdump showed that jabberd tried to send packets to the clients, but got no reply. Probably due to the client's firewall setup, it didn't get a RST or port/host unreachable. So it took a fairly long time until the tcp connection timed out and the server noticed the client went offline. Even worse, messages sent to this contact during the time he was 'offline without notice' got lost. I assume the jabber server already pushed them to the tcp stream and assumed they got delivered. A first step towards a solution would be shortening the tcp timeout. I don't know much about tcp programming, but I think it's possible for an application to set the timeout? Jan _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
