No type attribute means it is a message of type 'normal'

Julian

On Wednesday, Jul 9, 2003, at 05:42 US/Eastern, David Banes wrote:

Great thanks. I just realised that maybe Nitro does not set this and I'm
defaulting to 'normal' as it's value in my code is zero.


David.


In <[EMAIL PROTECTED]> Julian Missig wrote:
Um.

Oops.

That's something I need to work on (fixing up the message events JEP).

In my spiffed-up version of JEP 0022, I'll say that the type should
match the type of the message the event is in reference to. So it
should be 'chat' for chat messages and 'normal' for normal messages.

Julian

On Tuesday, Jul 8, 2003, at 07:42 US/Eastern, David Banes wrote:

Hi,

I notice that Exodus and the Jabber.com Win32 clients send message
events (composing etc) with a msg type of 'chat' whereas the OSX
Nitro client sends them as 'normal'.

Which is the correct or preferred implementation?

Thanks

David.


_______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev

_______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev

Reply via email to