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
-- Fabio Forno - PhD Student Politecnico di Torino - Dip. Automatica ed Informatica C.so Duca degli Abruzzi 24 - 10129 Torino (Italy) Phone: +39 011 564 7137 - JabberId: [EMAIL PROTECTED]
_______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
