On 3/28/06, Michal Vaner (Vorner) <[EMAIL PROTECTED]> wrote: > Dne úterý 28 březen 2006 07:06 Vinod Panicker napsal(a): > > Hi, > > > > Just wanted to check with the server implementors - Do you allow > > multiple "connected" resources with the same resource identifier? > > According to to specification, resource must be unique, therefore it is not > allowed to have two same resources.
There's no such requirement in the RFC. In fact, the RFC states that a server may allow multiple "connected" resources with the same resource identifier. > > If yes, how do you handle delivery of <iq/> stanzas addressed to the > > full jid of the user. > > > > If no, how do you handle it when a client connects with a resource > > identifier that is already in use? > > There are three possible ways on the server, two on the client side. > > On the client side, the client may set the resource to something or let the > server choose something for him. > > On the server side, it is possible to drop the old (which is more logic, it > can be some hanging connection that did not timeout yet), drop the new one or > change the wanted resource. Yes, server can return different resource than > client asked for and in this case, it may be a good solution sometimes. I myself prefer that the server return a <conflict/> to the OLD connection and not the new one. Regards, Vinod.
