On Thursday August 25 2005 19:03, Stephen Marquard wrote: > Gaston Dombiak wrote: > > Hey Daniel, > > > > The disco packet that Jive Messenger is sending to the newly connected > > external component is meant for discovering if a new item should be added > > to the disco#items packet that the server sends back when someone tries > > to discover the server's items. So that disco info is not being used for > > binding domains to the new component. > > > > Jive Messenger is implementing JEP-114 where the TO attribute of the > > opening stream indicates the domain of the new service provided by the > > component. AFAIK, jabberd2 elaborated another component JEP > > (http://jabberd.jabberstudio.org/dev/docs/component.shtml#sect-id2593096) > > that allows to bind one or more domains for one component but JM does not > > support that "proto"-JEP. > > Is anyone interested in this becoming a real JEP rather than j2 internal > documentation, i.e. would it be worth the effort to submit it to the JEP > process?
When I added support for JEP-0114 to gloox I somewhat missed TLS and SASL. I'd like this proto JEP become a real one and gloox will certainly support the current version and successors in one of the next releases. cheers, Jakob
pgp5yiJJ1p6UI.pgp
Description: PGP signature
_______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
