(sorry for sending off-list first, I changed email clients) On 2010-01-29 13:39, Jonathan Schleifer wrote: > Hm, this sounds to me like killing resources all together. Why not let > the user decide? For example, if the user gives all resources the same > priority, all resources get the message. If the user decides to use > different priorities, only the one with the higehst gets it (if 2 are > sharing the highest prio, both should get it). And this already works in current draft, because section 8.3.1.1 says: If there is not one highest-priority available resource but instead the highest priority is asserted by two or more available resources, these resources are said to form a "delivery tie". In the case of a delivery tie, a server SHOULD deliver the message to all of the tied resources. while old 11.1 said: If two or more available resources have the same priority, the server MAY use some other rule (e.g., most recent connect time, most recent activity time, or highest availability as determined by some hierarchy of <show/> values) to choose between them or MAY deliver the message to all such resources. So with current draft, user can decide if they want to get message delivered to all resources (by setting same priority), or to only one resource (by setting different priorities). If most people think that delivering everywhere is a better default, then recommend clients to use priority 0 / no priority by default. > I think priorities and resources are one of the killer features of XMPP > and should not be removed or crippled. +1 -- Maciek xmpp:machekku at uaznia.net
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.