[Standards] About stream namespaces

Peter Saint-Andre stpeter at jabber.org
Fri Mar 16 18:01:37 UTC 2007

Robin Redeker wrote:
> On Fri, Mar 16, 2007 at 11:51:24AM -0600, Peter Saint-Andre wrote:
>> Robin Redeker wrote:
>>> On Fri, Mar 16, 2007 at 11:12:59AM -0600, Peter Saint-Andre wrote:
>>>> Robin Redeker wrote:
>>>>> Enforcing this kind of backward compatibility for new client
>>>>> implementations does not make much sense for me. It would make more
>>>>> sense if servers would would be told that they MAY not generate
>>>>> such prefixes to take care of old clients.
>>>>> At least with that SHOULD NOT in place this issue will never be
>>>>> resolved because server implementors might say: "Well, RFC says you
>>>>> SHOULD NOT do that. I won't fix it.". And client developers will
>>>>> have to obey :-)
>>>> One of our rules in writing the RFCs was not to break things since we 
>>>> already had such a large installed base at that time. Sorry.
>>> Does this mean that these issues will never be resolved, because there
>>> are already so many people who do it wrong?
>> Maybe we'll fix them in XMPP 1.1 or 2.0. But my standard line is that I 
>> sure hope I'm not around to work on those...
> *sigh* ok ;-/

It's that people have been unaware of the problem for a long time:


It's just that we have inertial issues...


Peter Saint-Andre
XMPP Standards Foundation

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

More information about the Standards mailing list