remote chatroom joining
stpeter at stpeter.im
Wed Nov 7 21:39:37 UTC 2007
Martin Atkins wrote:
> Peter Saint-Andre wrote:
>> Martin Atkins wrote:
>> Typically if you want users from foreign domains to access your add-on
>> service then you would publish a DNS record like this (the example is
>> from the jabber.org DNS setup, where we have a MUC service called
>> conference IN A 188.8.131.52
> Thanks for the correction.
> However, I'm confused about your distinction between "an XMPP
> server that listens on port 5269" and "add-on service hosted by the
> XMPP server at domain.com".
> If I send stanzas to anything in the domain conference.jabber.org, (and
> please correct me if I'm wrong here!) my own server will connect to
> 184.108.40.206 and start a stream like this:
> <stream to="conference.jabber.org">
> This leads me to consider that 220.127.116.11 is "a host handles XMPP
> S2S connections for both jabber.org and conference.jabber.org on TCP
> port 5269".
> What distinction are you making between these two things? Is it that
> conference.jabber.org doesn't accept C2S connections but jabber.org
> does? Surely that's what the _xmpp_client._tcp SRV records are for?
I mean that conference.jabber.org doesn't accept s2s connections. Now
they are hosted at the same IP address so it doesn't really make any
difference I suppose. Perhaps this is indeed an implementation detail.
I'll have to think about the DNS SRV implications, but in general we do
not recommend that you create a DNS SRV entry for services, only for the
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.danga.com/pipermail/djabberd/attachments/20071107/4ebb1d82/smime-0001.bin
More information about the Djabberd