[Standards] NEW: XEP-0225 (Component Connections)

Peter Saint-Andre stpeter at jabber.org
Fri Aug 10 17:37:41 UTC 2007

Ralph Meijer wrote:
> jabber:server and jabber:client both don't make much sense
> for component streams. I think we have a couple of choices here:
>  1. Use a separate namespace for the component streams.
>  2. Choose from jabber:server and jabber:client
>  3. Iff we do a new version of XMPP (i.e. >1.0), we could choose one
> namespace for all connections.
> I strongly prefer 1 over 2, 

I prefer that too. Not sure I strongly prefer just yet. :)

> but if we do 2, I'd choose jabber:server.

I'm agnostic on that. Either way, we're forcing a square peg into a
round hole.

> Option 3 is something that could be considered, but if you want to be
> interoperable with client and server implementations that implement
> versions <=1.0, you still have to do some juggling at the edges. However
> you would change the namespaces to and from that new namespace and use
> the new namespace internally.

We've always tried not to break older software. I see no good reason to
change that policy now.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7354 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070810/678a1b14/attachment.bin>

More information about the Standards mailing list