The main problem with resources is that they're already being used for other things with components. MUC uses them for nicknames for example. So if for some hypothetical reason you had 3 external MUC implementations that needed to use the same JID and they had to bind with a resource, that would get confusing quick. [EMAIL PROTECTED]/instance1/mynickname ? (I don't think that's a scenario that would come up, but hey.. just siting an example of where a component uses resources already)
Daniel ----- "Ralph Meijer" <[EMAIL PROTECTED]> wrote: > On Wed, 2008-01-30 at 17:23 -0700, Peter Saint-Andre wrote: > > If this is a second instance, the server could return an indication > of > > that fact using something like a resource: > > > > <iq id='bind_1' type='result'> > > <bind xmlns='urn:xmpp:tmp:component'> > > <hostname>chat.example.com</hostname> > > <instance>8ba991jag</instance> > > </bind> > > </iq> > > Huh, what? Why not be consistent and reuse the concept of resources? > > -- > Groetjes, > > ralphm
