On Mon, May 4, 2009 at 11:27 PM, Peter Saint-Andre <[email protected]> wrote: > -----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 <[email protected]> >> 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? >
Not sure. Perhaps. Though on the other hand pings are such a simple concept, anyone who needs to be told how to use them probably shouldn't be using them (and using a library instead) :) Matthew.
