[jdev] Re: Auto-configured external gateways

[Norman Rasmussen]

Well it would be usefull to be able to use more than 1 domain per
connection, and the only way that it's going to work
cross-implementation is if it becomes a proper JEP right?

On 25/08/05, Stephen Marquard <scm at marquard.net> 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?
> 
> Regards
> Stephen
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mail.jabber.org/mailman/listinfo/jdev
> 


-- 
- Norman Rasmussen
 - Email: norman at rasmussen.co.za
 - Home page: http://norman.rasmussen.co.za/