[jdev] if anyone is having problems with slow propogation for <x xmlns="MY_NAMESPACE" messages...

Matthias Wimmer m at tthias.net
Wed Nov 30 15:02:21 CST 2005


Hi Larry,

Kirschner, Larry schrieb:

> ...no matter what I tried, these message would start to propogate very 
> slowly after I had sent the first few.
>
> Just discovered something interesting with jabber1.4.3 and muc 0.6.0.
>
> I finally tried a test where I sent regular messages with a <body> and 
> those propogated normally. I experimented a bit and now I'm doing this:
>
> <message>
> // this dummy body element seems to make jabber happy
> // it doesn't work if you just send <body/>
> <body>1</body>
> <x xmlns="mtvn/games">
> // game event payload here
> </x>
> </message>
>
> ...and propogation speed is back to normal.
>
> I didn't look into jabber's internals at all to figure out why this 
> might be so. Just thought I'd put it out there in case anyone comes 
> across a similar problem.
>

This is a very interesting observation. For jabberd14, I do not see why 
this should make a difference. Jabberd14 does not care about the content 
of a message. It does not even check for the <body/> element inside a 
message as long as it does not get stored offline because it arrives for 
a user, that is currently not online. – But I am not sure how 
mu-conference handles the <body/> element. It might be interesting to 
look in the code of mu-conference. I will do that later … that's really, 
really interesting.

Tot kijk
Matthias



More information about the JDev mailing list