"Mike Mahoney" <mmahoney at palantirisystems.com> wrote: > +1 to specifying a default of 0. There was some talk on JDev > recently about binding multiple resources on one stream. In those > cases it would make a lot of sense to use priorities and deliver > appropriately. Oh, and while we're at it: It would also make sense to have some status based priority. I think most users will be even happier with that than broadcasting. The idea is to have a standard which status should mean which priority by default. That way, a user will always get messages to the resource where he is available. Examples: DND = 10 N/A = 20 Away = 30 Available = 40 Chatty = 50 This way, the user will automagically get it to the right resource. If two clients are online and active, he will get it to both. If he got auto-away at one, he will only get it to the resource that's still available. Gajim for example does it like this and this has always been doing what I wanted when I was using multiple machines. -- Jonathan
Attachment:
signature.asc
Description: PGP signature
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.