On Tue, Oct 28, 2008 at 3:41 PM, Pedro Melo <[EMAIL PROTECTED]> wrote: > > On Oct 28, 2008, at 5:23 AM, Sergei Golovan wrote: >> >> There's another extension (and it's even implemented): >> http://code.google.com/apis/talk/jep_extensions/roster_attributes.html > > No, the router part of your server doesn't need to look into the query part > of the IQ in this case. Only the session manager.
It doesn't matter which part of the server will process the stanza. The problem is that if you really want to forbid XMLNS prefixes in XMPP than this particular extension will be considered as a violation. And consequently it wouldn't be possible to extend XMPP by adding custom attributes (properly namespaced) to existing elements. If it's OK then go ahead. > > In some servers, those two parts are quite separate entities. > >> And there's an extension which requires to parse every message packet >> which goes through a server: >> http://www.xmpp.org/extensions/xep-0079.html > > Maybe a reason why I don't know of a single server who implements this. I guess it's just useless. At least in ejabberd (which creates a DOM for every incoming stanza) impementing this XEP seems not to be a big problem. -- Sergei Golovan
