The following thought for the day arises from a conversation I had
with Kevin Smith; so whilst all opinions and mistakes are my own,
this is heavily influenced by Kevin.
The behaviour for different <message/> types is different, by design.
In particular, when sent to a non-existent resource:
headline - broadcast.
error - discard.
normal/chat - highest priority, offline, or error.
Now, groupchat messages are currently handled as normal/chat. But
should they be?
The only circumstance I can think of where this might happen is if a
client joined to a MUC room goes away without, somenoe the presence
type='unavailable' getting through, which (in turn) might happen due
to a server bug, or crash.
Current rules dictate that the <message type='groupchat'/> will end
up going to a new resource, which won't know how to handle them.
So, should servers be rerouting anyway?
And, perhaps more interestingly, what should a client which receives
an unexpected type='groupchat' be doing with it? (Currently, most
clients appear to discard them silently).
Dave.
--
Dave Cridland - mailto:[EMAIL PROTECTED] - xmpp:[EMAIL PROTECTED]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
