On 2/11/09 10:51 AM, Waqas Hussain wrote: > Hi, > > 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 > <http://xmpp.org/internet-drafts/draft-saintandre-rfc3921bis-07.html#rules-fulljid-nomatch> > "For a message stanza, the server SHOULD treat the stanza as if it > were addressed to <u...@domain> as described in the next section (but > without modifying the value of the 'to' attribute)." > > 8.3.1.1. Message > <http://xmpp.org/internet-drafts/draft-saintandre-rfc3921bis-07.html#rules-barejid-resource-message> > "For a message stanza of type "chat", "error", "groupchat", or > "normal", the server SHOULD deliver the stanza to the highest-priority > available resource."
Fixed: http://svn.xmpp.org:18080/browse/XMPP/trunk/internet-drafts/draft-saintandre-rfc3921bis-09.xml?%40diffMode=u&%40diffWrap=s&r1=2960&r2=2961&u=3&ignore=&k= Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
