<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7233.28"> <TITLE>if anyone is having problems with slow propogation for <x xmlns="MY_NAMESPACE" messages...</TITLE> </HEAD> <BODY>  Just discovered something interesting with jabber1.4.3 and muc 0.6.0. I've been having a problem with my jabber install where it's only allowing messages at a rate of about 1 every 2 seconds and dropping messages in between. I thought the problem was karma or maybe something in the config. What I finally figured out is that jabber just doesn't like <message> messages that don't have a non-empty <body> element. What I had been sending were game-event messages that looked like this: <message>         <x xmlns="mtvn/games">         // game event payload here         </x> </message>                 ...no matter what I tried, these message would start to propogate very slowly after I had sent the first few. 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. --Larry </BODY> </HTML>