[jdev] Re: Query regarding development

[Stephen Marquard]

Peter Saint-Andre wrote:
> On Thu, Feb 24, 2005 at 09:52:57PM -0800, Justin Karneges wrote:
> 
>>On Thursday 24 February 2005 09:35 pm, Krishna Prashanth wrote:
>>
>>>Thanks for all the information. Since I have said above that I would
>>>want to develop a component (I have also read most of jabber's
>>>documentation), is plugging in a component consistent across all jabber
>>>servers? I am more interested in jabberd-1.4.3 and jabberd2. I have also
>>>used wpjabber in the past. Awaiting your reply.
>>
>>I believe the component protocol is different for both jabberd1 and jabberd2.  
>>If you want to allow wide use of your component, you might consider doing it 
>>the jabberd1 way (which is also formalized in JEP-0114).  The jabberd2 
>>component protocol is more powerful, but specific to jabberd2.
> 
> jabberd2 also supports JEP-0114, no?

Yes, though a question came up recently about how components identify to 
j2 the domain for which they should receive packets.

JEP-0114 shows a stream header of a component being:

<stream:stream
     xmlns='jabber:component:accept'
     xmlns:stream='http://etherx.jabber.org/streams'
     to='plays.shakespeare.lit'>

whereas at least one implementation (mu-conference + jcr) uses something 
like:

<stream:stream
     xmlns='jabber:component:accept'
     xmlns:stream='http://etherx.jabber.org/streams'
     from='audience.plays.shakespeare.lit'
     to='plays.shakespeare.lit'>

when talking to jabberd2, i.e. includes its own domain in the from 
attribute on the stream header.

I wondered whether the JEP needs updating ?

Regards
Stephen