[Standards] XEP-0073: Question about service discovery

Peter Saint-Andre stpeter at jabber.org
Wed Feb 7 18:07:41 UTC 2007

Robin Redeker wrote:
> On Wed, Feb 07, 2007 at 01:53:43PM +0100, Remko Tronçon wrote:
>>> So even if clients implement XEP-0115 they still have to send out
>>> (without caching) jabber:iq:version and the disco request
>>> when someone goes online.
> [.snip.]
>> Clients used to do jabber:iq:version requests to display which client
>> a contact is using in their UI. This of course causes floods of iq
>> requests when you sign on, which is bad. This is no longer necessary
>> with capabilities, since you can derive this from the caps node in the
>> presence, and the client name in the cached disco#info request. 
> And what about XEP-0073? It does not require XEP-0115 for the basic
> protocol suite. So a client implementing only the basic protocol suite
> will cause lots of flooding (he doesn't know how and what to cache
> and so sends disco#info and jabber:iq:* requests to anyone).

So we'll add XEP-0115 to XEP-0073. :P

> And about jabber:iq:version: Looks like clients will still flood them
> if they want to display the OS the contact is using.

Why is the OS any of your business?


Peter Saint-Andre
XMPP Standards Foundation

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070207/fe27ce11/attachment.bin>

More information about the Standards mailing list