[JDEV] Is this bug fixed after 1.2 ?

[Dennis Noordsij]

On Tuesday 09 January 2001 01:22, Keith Minkler wrote:
> perhaps I can offer some assistance...
>
> In versions of the jabber server, pre 1.4pre1, the <ns/> tag has been
> broken... the deliver logic fell short when it came to flags like this, and
> the <warn/> <notice/> <alert/> flags... the 1.4pre1 server has had its
> deliver() logic changed, and this should be fixed now.. from what you said
> in this post, it looks like the xdb packet was infact delivered to BOTH of
> your xdb componenets.. (both xdb_file, and your external handler)...
>
> I haven't had a chance to fully look over the new deliver code, (it was
> written when i was on vacation, and i haven't quite caught up yet) =[, but
> this was supposed to be fixed in the new deliver logic..
>
> What version of the server were you using for this xdb test, btw?

Few notes:

Someone already mentioned this as a weird bug, ie xdb_set after xdb_get 
segfaulting jabber in some cases :(

I was using Jabber 1.2

Last night I tried jabber2 from CVS (1.3?), if I have 2 xdb entries (similar 
to my example, no namespaces <ns> tags) NONE of them receive anything and 
jabber claims it can not deliver to anything. If I only have one xdb entry, 
be it xdb_file or external handler everything works (apart from changing for 
example user at host/jabber:x:offline to user at host ns='jabber:x:offline'

Weird weird :-)

Regards,
Dennis