Isn't that a TCP problem since that can happen to any protocol which is based to TCP?<br><br><div><span class="gmail_quote">On 11/1/06, <b class="gmail_sendername">Scott Robinson</b> <<a href="mailto:scott@tranzoa.com">
scott@tranzoa.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">What is the proper method of performing a ping across a client XMPP
<br>connection. That is, from a sever's perspective, if a client<br>mysteriously and unexpectedly drops off the Internet, it won't know it<br>until the TCP connection times out.<br><br>This obviously can lead to two inconvenient situations:
<br> 1. Dropped messages that could otherwise stored.<br> 2. A stale presense of availablity.<br><br>A quick Google search didn't result in anything useful, except a thread<br>noting how it _shouldn't_ be done.<br><br>Any ideas?
<br><br>--<br>Scott Robinson <<a href="mailto:scott@quadhome.com">scott@quadhome.com</a>><br><a href="http://quadhome.com/">http://quadhome.com/</a><br><br><br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.2.5 (GNU/Linux)
<br><br>iEYEARECAAYFAkVH7w8ACgkQ2wcaZqTSGsTUygCg1PrqPL5KBGe6kFEmAAL003yu<br>djsAoKIAXlj00sRoFpI/WqIVUL9hpFOV<br>=tucZ<br>-----END PGP SIGNATURE-----<br><br><br></blockquote></div><br>