[Standards] groupchat and error message routing

Waqas Hussain waqas20 at gmail.com
Wed Feb 11 17:51:56 UTC 2009


When messages of type 'groupchat' and 'error' are sent to a
non-existing resource, they are routed to the set of highest priority
available resources. IMHO this behaviour in counter-intuitive. I don't
see why an unintended resource would want a groupchat or error
message, or how it's supposed to deal with it. Also note that the 'to'
attribute gets overwritten, so the recieving resource doesn't even
know to which resource the messages were originally directed. Could
someone describe some cases where this is useful?

Relevent rfc3921bis-07 sections:

8.2.2.  No Resource Matches
"For a message stanza, the server SHOULD treat the stanza as if it
were addressed to <user at domain> as described in the next section (but
without modifying the value of the 'to' attribute)."  Message
"For a message stanza of type "chat", "error", "groupchat", or
"normal", the server SHOULD deliver the stanza to the highest-priority
available resource."

Waqas Hussain

More information about the Standards mailing list