On Tue Apr 27 23:09:25 2010, Peter Saint-Andre wrote:
I assume that even if we allowed 'jabber:client' stanzas over
'jabber:server' streams, we would not allow 'jabber:server' stanzas
over
'jabber:client' streams. At which point everything becomes
'jabber:client', in a way...
Except subtly
On Wednesday 28 April 2010 04:05:32 Dave Cridland wrote:
Besides which, it's really not that much effort on the part of the
server to translate between namespaces, surely?
It's awkward usage of XML. I'd like to phase out such usages that cause
people to react with what were they thinking?.
On Wed Apr 28 17:59:17 2010, Justin Karneges wrote:
On Wednesday 28 April 2010 04:05:32 Dave Cridland wrote:
Besides which, it's really not that much effort on the part of the
server to translate between namespaces, surely?
It's awkward usage of XML. I'd like to phase out such usages that
On Wed, Apr 28, 2010 at 09:59:17AM -0700, Justin Karneges wrote:
On Wednesday 28 April 2010 04:05:32 Dave Cridland wrote:
Besides which, it's really not that much effort on the part of the
server to translate between namespaces, surely?
It's awkward usage of XML. I'd like to phase out
In XMPP, each stream has a default namespace. Stanzas are the
elements with local-name message, presence, or iq, qualified by
that default namespace. Streams also have other, specifically
documented, top-level elements, such as those for SASL, or TLS
negotiation - these being explicitly
Hi,
On Tue, Apr 27, 2010 at 10:00 AM, Dave Cridland d...@cridland.net wrote:
There has since been some (unfortunately public) suggestions that not
accepting client stanzas on an S2S stream is a bug in M-Link, so I'd like to
seek other opinions on the correct behaviour.
How would client
Hi,
I normally don't participate to such discussions because they tend to be
lengthy with no practical outcome.
However, I encountered a few problems related to xmlns handling recently both
with jabber.org (M-Link)
and transports and also with XEP-0225.
I think sharing my thought and
Excerpts from Artur Hefczyc's message of Tue Apr 27 15:56:24 +0100 2010:
Hi,
I normally don't participate to such discussions because they tend to be
lengthy with no practical outcome.
However, I encountered a few problems related to xmlns handling recently both
with jabber.org (M-Link)
On 4/27/10 3:00 AM, Dave Cridland wrote:
In XMPP, each stream has a default namespace. Stanzas are the elements
with local-name message, presence, or iq, qualified by that
default namespace. Streams also have other, specifically documented,
top-level elements, such as those for SASL, or TLS
On Tue, Apr 27, 2010 at 9:18 PM, Peter Saint-Andre stpe...@stpeter.im wrote:
On 4/27/10 3:00 AM, Dave Cridland wrote:
In XMPP, each stream has a default namespace. Stanzas are the elements
with local-name message, presence, or iq, qualified by that
default namespace. Streams also have other,
On 4/27/10 8:56 AM, Artur Hefczyc wrote:
My understanding of the spec is that it defines a default namespace
for top level elements but it does not forbids you from sending
elements within a different namespace as long as this different
namespace can be understood.
This is ambiguous in the
On Tue, Apr 27, 2010 at 9:34 PM, Peter Saint-Andre stpe...@stpeter.im wrote:
On 4/27/10 2:30 PM, Kevin Smith wrote:
On Tue, Apr 27, 2010 at 9:18 PM, Peter Saint-Andre stpe...@stpeter.im
wrote:
On 4/27/10 3:00 AM, Dave Cridland wrote:
In XMPP, each stream has a default namespace. Stanzas are
Note: Because a client sends stanzas over a stream whose default
namespace is 'jabber:client', if the server to which the client is
connected needs to route a client-generated stanza to another server
then it MUST re-scope the stanza so that its default namespace is
'jabber:server' (i.e., it MUST
Dnia 2010-04-27, wto o godzinie 15:56 +0100, Artur Hefczyc pisze:
My understanding of this is that: the server supports both
jabber:client and
jabber:server namespaces.
'OR' returns false if both sides of the OR are false. Therefore, if
the server
receives jabber:client packet over s2s
On 4/27/10 4:06 PM, Tomasz Sterna wrote:
Dnia 2010-04-27, wto o godzinie 15:56 +0100, Artur Hefczyc pisze:
My understanding of this is that: the server supports both
jabber:client and
jabber:server namespaces.
'OR' returns false if both sides of the OR are false. Therefore, if
the server
15 matches
Mail list logo
