[jdev] Re: Auto-configured external gateways
jadestorm at nc.rr.com
Thu Aug 25 12:30:24 CDT 2005
I wholeheartedly agree! My particular software, for example, would
benefit greatly from it due to the way AIM handles it's chat "exchanges".
IE, it would be very helpful for me to be able to say that I am all of the
Without having to open 18 different connections to the main server. As it
stands right now, I think I'm willing to open 2, but I'm definitely not
going to open 18.
"The most addictive drug in the world is music."
- The Lost Boyz
> 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
>> > 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
>> > stream indicates the domain of the new service provided by the
>> > 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
>> > 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
>> jdev mailing list
>> jdev at jabber.org
> - Norman Rasmussen
> - Email: norman at rasmussen.co.za
> - Home page: http://norman.rasmussen.co.za/
> jdev mailing list
> jdev at jabber.org
More information about the JDev