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.
I'm a bit torn about this, comments inline.
On Wed, 2007-08-08 at 15:11 -0700, Justin Karneges wrote:
On Wednesday 08 August 2007 1:44 pm, Peter Saint-Andre wrote:
XMPP Extensions Editor wrote:
Version 0.1 of XEP-0225 (Component Connections) has been released.
Abstract: This document
Hello,
i am for jabber:client because i don't like the namespace switching in
software.
But this does not help that much if we stick with other namespaces on
s2s connections forever.
Alex
Hi Justin!
Justin Karneges schrieb:
I don't have a strong preference really. A component feels a bit more
like a client because it is a local connection, plus c2s connections are
simpler than s2s connections. Let's pick one and be done with it. :)
The reason why I for the most part suggest
Dnia 10-08-2007, pią o godzinie 10:26 +0200, Matthias Wimmer napisał(a):
But I'd prefere to use 'jabber:server'. Even if have a bit of
the expression, that people merely prefere 'jabber:client' just
because
more people seem to work on clients or client connections were they
are
more used
Hello
On Fri, Aug 10, 2007 at 11:19:59AM -0700, Justin Karneges wrote:
That said, all server implementations need to do this namespace juggling
anyway, so I don't see how it is an extra burden to do this for another
namespace, too.
What doesn't sit well with me is this idea of the
Dnia 08-08-2007, śro o godzinie 15:11 -0700, Justin Karneges napisał(a):
I vote not repeating this mistake. This means
no 'jabber:component' or such. The choice should be between
'jabber:client'
and 'jabber:server' for the namespace. Use a real attribute or
element to
indicate
Tomasz Sterna wrote:
Dnia 08-08-2007, śro o godzinie 15:11 -0700, Justin Karneges napisał(a):
I vote not repeating this mistake. This means
no 'jabber:component' or such. The choice should be between
'jabber:client'
and 'jabber:server' for the namespace. Use a real attribute or
element
Hi Peter!
Peter Saint-Andre schrieb:
I don't have a strong preference really. A component feels a bit more
like a client because it is a local connection, plus c2s connections are
simpler than s2s connections. Let's pick one and be done with it. :)
The reason why I for the most part suggest
XMPP Extensions Editor wrote:
Version 0.1 of XEP-0225 (Component Connections) has been released.
Abstract: This document specifies a standards-track XMPP protocol
extension that enables server components to connect to XMPP servers.
One of the items up for discussion is the default namespace
On Aug 8, 2007, at 1:44 PM, Peter Saint-Andre wrote:
XMPP Extensions Editor wrote:
Version 0.1 of XEP-0225 (Component Connections) has been released.
Abstract: This document specifies a standards-track XMPP protocol
extension that enables server components to connect to XMPP servers.
One
Rachel Blackman wrote:
On Aug 8, 2007, at 1:44 PM, Peter Saint-Andre wrote:
XMPP Extensions Editor wrote:
Version 0.1 of XEP-0225 (Component Connections) has been released.
Abstract: This document specifies a standards-track XMPP protocol
extension that enables server components to
On Wednesday 08 August 2007 1:44 pm, Peter Saint-Andre wrote:
XMPP Extensions Editor wrote:
Version 0.1 of XEP-0225 (Component Connections) has been released.
Abstract: This document specifies a standards-track XMPP protocol
extension that enables server components to connect to XMPP
13 matches
Mail list logo
