[jdev] Re: Auto-configured external gateways
Gaston Dombiak
gaston at jivesoftware.com
Fri Aug 26 14:26:54 CDT 2005
Hey Stephen,
When Matt and I read jabberd2's component JEP we liked many things. :) I
think that in general the JEP is fine but we may need to discuss sections
3.5 and 3.6 (and maybe 3.7). We can start a new thread to discuss this JEP
and also discuss how to improve the existing JEP. One thing that none of the
these JEPs discuss is disco which I think it should be added.
Regards,
-- Gato
"Stephen Marquard" <scm at marquard.net> wrote in message
news:dektih$64b$1 at sea.gmane.org...
> 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
More information about the JDev
mailing list