В сообщении от Вторник 28 Март 2006 10:45 Vinod Panicker написал(a): > On 3/28/06, Alexey Nezhdanov <[EMAIL PROTECTED]> wrote: > > В сообщении от Вторник 28 Март 2006 09:06 Vinod Panicker написал(a): > > > Hi, > > > > > > Just wanted to check with the server implementors - Do you 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? > > > > xmppd.py not allows that and drops previous connection with <conflict/> > > stream error. > > According to RFC 3920, in this case, the server should return a > <conflict/> to the new connection. > > From section 7 : > > Client binds a resource: > > <iq type='set' id='bind_2'> > <bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'> > <resource>someresource</resource> > </bind> > </iq> > > Resource identifier is in use: > > <iq type='error' id='bind_2'> > <bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'> > <resource>someresource</resource> > </bind> > <error type='cancel'> > <conflict xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/> > </error> > </iq> > > Note that the <conflict/> error is sent to the new resource and not > the currently connected one. Well, I just do not remember. Probably it behaves exactly then. I have leaved xmppd.py long ago, but at that time I was consulting with RFC for every case.
> Regards, > Vinod. -- Respectfully Alexey Nezhdanov
