Parser borrowing not XML-compliant

[Brad Fitzpatrick]

I was wondering if this would happen.

Yeah, perhaps the default behavior should be to not share parsers until we
figure this out properly, tracking the namespace status per parser.


On Fri, 22 Sep 2006, Mika Raento wrote:

> Hi
>
> I've been playing with djabberd as an option for Jaiku ( www.jaiku.com/
> ), and it seems nicely modifiable. I however got a problem as soon as I
> connected two different clients: we use our own extensions in Jabber,
> with our own namespace which we declare on the stream element.
>
> Now if parsers are borrowed, the parser we get may not have the right
> namespace.
>
> I'm working around this by calling set_config_shareparsers(0). The
> 'right' way to do it (if you do want to share parsers) is for the
> connection's namespace to be dynamic, and based on what the client sends.
>
> So what's up with djabberd anyway? Not much traffic on the list.
>
> 	Mika Raento
>
>