Peter Saint-Andre wrote:
Hi,
I'm analyzing some messages logged by a component received with the option "archive", and I see that all the messages with a composing event are duplicated. Has anyone an idea of why this is happening?
What client were you using? Most implementations of JEP-0022 get it
wrong (I read XML debug, so I know). That's one reason Dizzy and I wrote
JEP-0085 -- there are just too many ambiguities and undefined cases in
the message events protocol (even after I cleaned up the documentation that's in the JEP earlier this year). I'm working to encourage the Jabber Council to decide between the two protocols in the near future.
Sorry for delay, but I missed the reply. I was using no clients, but just getting raw XML to a component for logging purposes. Accordingly to my logs all double messages came from Exodus, but I don't know whether this was due to the client (not under my control) or the server.
Now I'm looking for someone using Exodus here around in order to sniff some raw XML ;)
I've got Exodus, but mainly use Gaim. kirjava [at] jabber (dot) orgggg (remove some gggg's ;)) (as that is also an E-Mail Account, and can be spammed...
-- From Ren� S. C. Bartosh <[EMAIL PROTECTED]>
About me, contact details, programs, blog etc: http://kirjava.net.nz/ _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
