[jdev] Gaim and gnomemeeting using jabber

[PUYDT Julien]

Le lundi 06 décembre 2004 à 09:11 +0000, Richard Dobson a écrit :
> Well before we had JEP-0115 clients that supported disco and wanted to
> find out what other clients supported would send the disco request to any
> people as they become available (i.e. receive an available presence stanza
> from them), but this was a bit bandwidth intensive and could cause a bit of
> a flood of requests when a user logged on, so JEP-0115 was developed so that
> you could help avoid this flood of requests everytime because it would tell
> other clients in that first presence stanza they receive from you what your
> capabilities are so they dont need to necessarily flood you with disco
> requests as you have already told them what you support and can just use 
> their cache of the disco requests that link with the caps that you 
> published, this avoids them rerequesting disco infos everytime you log in.

Notice the above is one single sentence. Let me try to restate it
differently to see if my poor brain's parser did a decent job with it:

Before JEP-0115 was written, a connecting client would send a simple
presence message. That message would trigger the sending of disco
requests from all of its contacts, requests that it would have to handle
itself.

Now that JEP-0115 is there, a connecting client sends a more complex
presence message, where it states its capabilities. And even when the
contacts need more information on some piece, the server has a cache
that enables it to handle the load more easily.

That means that to make a client able to do voip, I would have to modify
it to:
* send voip capability declarations in presence ;
* handle disco requests about the voip (say callto and h323 are
supported, for example) ;
* recognize oob voip uris and trigger a voip call (receive the h323
adress of the im-caller -- which it sends because it knows I can do
that) ;
* recognize the voip capability declarations in others' presence.

Do I get it at least partially correct?

JP