Daniel Henninger wrote: > Hi folk! > > We have a need to connect multiple iterations of a component to the > same JID.
Currently, XEP-0225 talks about the same component binding multiple
hostnames, but it does not talk about multiple components binding the
same hostname. Whether that is allowed or disallowed, at least it needs
to be specified.
Some of this gets into server internals. We deliberately steered away
from that based on our discussions in Portland at DevCon #3. However, I
think we can at least specify the behavior here and let implementations
do with it what they will.
Right now a bind request looks like this:
<iq id='bind_1' type='set'>
<bind xmlns='urn:xmpp:tmp:component'>
<hostname>chat.example.com</hostname>
</bind>
</iq>
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>
(Where the instance is unique in the context of that hostname.)
What you do with the multiple instances is up to you.
On the other hand, if the server doesn't support multiple instances, it
would return a conflict error.
But I need to think about it some more...
Peter
--
Peter Saint-Andre
https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
