On Fri, Mar 12, 2010 at 11:52, Laurent Eschenauer <laur...@eschenauer.be> wrote: > Hi everyone, > > In onesocialweb, our use cases imply that all connected resources > should receive a message when sent to the bare JID. It is simple to > understand why: although your desktop client may be open, you may > still want your phone to vibrate when a new updates come in, and you > absolutely one that update to be visible in your 'inbox' when you pick > up your phone at a later time. > > Today, we can achieve this by using server specific logic (in > openfire: route.all-resources=true) but that has an impact on all > messages from all services (and we may want to keep the usual behavior > for chat, or whatever else). > > I was wondering if there was any possibility for the sender (client or > server) to specify that the message being sent should ideally be > broadcasted to all resources (having positive priority to complain > with the rest of the spec). > http://xmpp.org/rfcs/rfc3921.html#rules > > So, what about an additional "broadcast" message attribute for this ? > I think there are more uses cases where you may want to use XMPP as a > "messaging bus" between the connected resources of a user. > > Am I missing a point ? Any other work or proposal already tackling this ? > > Thanks for the feedback ! > > -Laurent
There is XEP-0033: Extended Stanza Addressing that might partially address your need: http://xmpp.org/extensions/xep-0033.html Also I'm not sure, but if you control all your client connections, you might want all resources to connect with the same priority (dirty hack?). -- Nicolas Vérité - ProcessOne http://process-one.net Mobile: +33 6 20 88 63 04
