-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 4/30/09 2:53 PM, Matthew Wild wrote: > On Thu, Apr 30, 2009 at 5:16 PM, Peter Saint-Andre <stpe...@stpeter.im> wrote: >> In its meeting yesterday, the XMPP Council agreed to issue a "Call for >> Experience" regarding XEP-0199 (XMPP Ping), in preparation for perhaps >> advancing this specification from Draft to Final in the XSF's standards >> process. To help the Council decide whether this XEP is ready to advance >> to a status of Final, the Council would like to gather the following >> information: >> >> 1. Who has implemented XEP-0199? Please note that the protocol must be >> implemented in at least two separate codebases (and preferably more). >> > > We have implemented it in Prosody. We don't actively use it (yet) but > correctly answer pings from clients and other servers.
Thanks for the report. > We are discussing using XMPP pings to check s2s connections are still > working prior to sending data after a long period of silence. As Dave > writes, relying on TCP is not enough for various reasons. > > We also intend to use it to ping clients prior to replacing them in a > resource conflict. Does it make sense to add some of these use cases to the spec under implementation guidelines or usage scenarios? Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn/a8QACgkQNL8k5A2w/vyGkgCgqNGsZrR9er3yvyKkNyfSWdBK 1o4AoMqsaEx4Y5t8cYhViNMM6POAlukw =kg9n -----END PGP SIGNATURE-----
