Hi David! David Waite wrote:
> This (together with the 'jabber:server' / 'jabber:component:accept' > namespace usage) would be rather difficult to fix at this point > without breaking interoperability with nearly every client, server, > and server component - many of these use custom parsers which do not > have any support for namespaces, and rely on a particular prefix just > like the open-source server. I don't see why this should break interoperability. The server just has to send the known prefixes and namespace declarations to the clients (which is perfectly well formed XML) and handle incoming XML with correct namespace processing. The only thing will be that this will consume more memory per user on the server because it has to store all the namespace definitions the client has send. Tot kijk Matthias And BTW: I hate it too, that jabberd doesn't handle the namespaces as it should. -- Fon: +49-700 77007770 http://matthias-wimmer.de/ Fax: +49-89 312 88654 jabber:[EMAIL PROTECTED] _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
