[JDEV] Messaging with Resources, desired behavior

Robert Norris rob at cataclysm.cx
Mon May 26 19:15:35 CDT 2003

> When I first send a message to someone, I send it to someone at jabber.com.
> The server then looks through (I'm assuming) what resources "someone" is
> logged in with, picks the one with the highest priority, and forwards
> the message to them. This means that the message actually is delivered
> so someone at jabber.com/HighPriorityResource.
> If/When they reply, so I quickly get a message back from
> someone at jabber.com/HighPriorityResource. 
> If I reply to that message, should I send it to the user at resource, or
> continue sending it to "user", and let the server make the resource
> priority decision on each and every message?

I guess it depends on whether or not the received message and the
"reply" is related. A reply sent from an IM client should probably use
the resource (because you want to get to a specific session, where you
know there is a person to read it), but some kind of middleware
application might want to just send to the user itself.

> More importantly, let's say someone at jabber.com/HighPriorityResource goes
> offline and I send him a message (using the full JID + Resource), but
> comes online at someone at jabber.com/DifferentResource - will the server
> automatically deliver the message to that resource, or will the message
> be archived for the next time (s)he logs in using that exact resource
> name?

The message will be bounced.

> Is this behavior concretely defined somewhere? I've looked, but couldn't
> find it...

Delivery rules are defined here:



Robert Norris                                       GPG: 1024D/FC18E6C2
Email+Jabber: rob at cataclysm.cx                Web: http://cataclysm.cx/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20030527/6db0e05d/attachment-0002.pgp>

More information about the JDev mailing list