> 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) cheers, Remko
