On Wed May 14 15:22:35 2008, JabberForum wrote:
What is special about the resource names that we cannot accomplish
just
by having a unique bare jid for both users (instead of the
users/clients
differing only by resource name)
There's only one user, so only one bare jid. Bare jids refer to
users, full jids refer to clients. Things get muddied when we're not
dealing with users or clients, mind.
It would be great if someone can give a 'real' example where the
resource names are useful compared to unique bare jids....
But that's the thing - users already do have unique bare jids. Full
jids allow a client instance to also be addressible, so both users,
servers, and clients are all fully and individually addressible.
For real examples of where this is useful, consider requesting data
from a restricted service. You need the chatroom to send the data
back to the same client, but you also need it to identify it's you.
The simplest method for doing both is to allow the user identifier
(bare jid) to be derivable from the client identifier (full jid), and
every full jid is securely bound to a bare jid.
Dave.
--
Dave Cridland - mailto:[EMAIL PROTECTED] - xmpp:[EMAIL PROTECTED]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
