[JDEV] Namespace usage on server
temas
temas at box5.net
Wed Oct 3 11:18:52 CDT 2001
Diz is right, we just need to make our parser in the next gen reference
implementation (and possibly a patch for 1.4.x) to fully understand
namespaces. The rest of this thread seems like a bit of
miscommunication or crossed wires. Let's fix this rather than argue
over it, we've identitified the problem.
--temas
On Wed, 2001-10-03 at 09:05, Dave Smith wrote:
> Actually, what you are seeing is broken behaviour in Jabber's handling
> of namespaces. In keeping with the XML 1.0 and XML Namespaces spec,
> specifying the namespace on a per packet basis is perfectly acceptable.
> Unfortunately, up to this point, the Jabber server doesn't process
> namespaces at all (at least, in a correct manner) and hence you get
> unexpected behaviour when you move the namespace declarations around.
>
> At some point, someone will have to fix this.. :)
>
> Diz
>
>
> On Wed, Oct 03, 2001 at 03:16:25PM +0200, Fabrice DESRE - FT.BD/FTRD/DMI/GRI wrote:
> > Hello,
> >
> > Writing my own client, I found something
> > strange in the open source server : if I
> > initiate the session with :
> > <?xml version='1.0'?>
> > <stream:stream to='jabber'
> > xmlns:stream='http://etherx.jabber.org/streams'
> > xmlns='jabber:client'>
> > <iq id='A3' type='get'>
> > <query xmlns='jabber:iq:auth'>
> > <username>fabrice</username>
> > </query>
> > </iq>
> > </stream:stream>
> >
> > everything works fine, but if I send :
> >
> > <?xml version='1.0'?>
> > <stream:stream to='jabber'
> > xmlns:stream='http://etherx.jabber.org/streams'>
> > <iq xmlns='jabber:client' id='A3' type='get'>
> > <query xmlns='jabber:iq:auth'>
> > <username>fabrice</username>
> > </query>
> > </iq>
> > </stream:stream>
> >
> > then the server sends me this error and closes the connection :
> > <?xml version='1.0'?>
> > <stream:stream xmlns:stream='http://etherx.jabber.org/streams'
> > id='3BBB0DE3'
> > xmlns='jabber:client'
> > from='jabber'>
> > <stream:error>Invalid Namespace</stream:error>
> > </stream:stream>
> >
> > I don't understand the rationale of this error message. My first XML
> > stream is perfectly valid and the QName of the elements are the same
> > in both cases.
> > I didn't find any mention of this requirement in the docs so I guess
> > it's a bug in the server ?
> >
> > Fabrice
> > --
> > Fabrice Desr? - France Telecom R&D/DMI/GRI
> > Tel: +(33) 2 96 05 31 43
> > Fax: +(33) 2 96 05 32 86
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20011003/2655d35e/attachment-0002.pgp>
More information about the JDev
mailing list