[jdev] Websockets RFC: stream: prefix required or not?
flo at geekplace.eu
Mon Feb 2 19:24:11 UTC 2015
On 02.02.2015 18:39, Michael Weibel wrote:
> Hi all,
> MongooseIM currently sends stream:features as „features“ for websockets connections and strophe.js doesn’t recognize this currently.
> How I read the RFC is that both behaviours (stream:features or just „features“) are correct:
>> Note that for stream features and errors, there is no parent context
>> element providing the "stream" namespace prefix as in [RFC6120], and
>> thus the stream prefix MUST be declared or use an unprefixed form:
>> <stream:features xmlns:stream="http://etherx.jabber.org/streams">
>> <bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"/>
>> -- OR --
>> <error xmlns="http://etherx.jabber.org/streams">
>> <host-unknown xmlns='urn:ietf:params:xml:ns:xmpp-streams'/>
> I think the example in the RFC is not perfect, it should instead show the format for both cases and I think that’s also the source of confusion.
> What is your opinion on this? Is MongooseIM or Strophe.js’ behaviour correct?
Doesn't this come down to the question if
And it appears to be that they are. So I'd say that strophe's behavior
is not correct.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 668 bytes
Desc: OpenPGP digital signature
More information about the JDev