Le mercredi 08 d�cembre 2004 � 09:31 +0000, Richard Dobson a �crit : > > If the other clients cache the capabilities... what happens when I > > upgrade my gnomemeeting that 'only' does h323 to the upcoming > > gnomemeeting that also does sip? > > Then I would suggest you send it as a different feature cap of "voipgm2" or > something else rather than "voip" and this time include both h323 and sip as > features in the response, e.g. > > <presence> > <c xmlns='http://jabber.org/protocol/caps' > node='http://exodus.jabberstudio.org/caps' > ver='0.9' > ext='ftrans xhtml voipgm2'/> > </presence> > > It doesnt matter what the cap string is so long as its nice and short, it > can be anything you like (so long as its not already used by that version of > the client), what matters is what you return in the disco#info response when > other clients query what it means.
Uh... bad: if I put the name of the voip client in the caps, I lose all the benefits of having several clients for the same protocol. Let's call it voip_h323 and voip_sip! JP _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mail.jabber.org/mailman/listinfo/jdev
