On 3/28/06, Remko Troncon <[EMAIL PROTECTED]> wrote: > > I myself prefer that the server return a <conflict/> to the OLD > > connection and not the new one. > > I always hated that behaviour. If i 'accidentally' connect with the wrong > resource, my resource on the other end of the building/city/world dies, > and there's no way to bring it back up. I would much rather try again > on the current resource. > > Anyway, these resource conflicts shouldn't happen in an ideal world: > a typical user should not need to bother with entering the resource, the > server should assign resources to connecting clients himself through > resource binding (like the google talk server does)
But what if the client being used doesn't allow resource identifiers to be changed? I like being able to logoff the current existing resource by logging in from a different location. And the whole point of the resource identifier was to be able to signify the location of the resource (home, work, mobile) rather than be a random bunch of characters. Regards, Vinod.
