remote chatroom joining

[Martin Atkins]

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.jabber.org:
> 
> conference   IN A   208.245.212.98
> 

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 
208.245.212.98 and start a stream like this:

     <stream to="conference.jabber.org">

This leads me to consider that 208.245.212.98 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 should note that I'm probably being biased here by DJabberd's 
"Everything is a VHost" ethos. I'm aware that in jabberd 1 there is a 
much stronger distinction between servers and their services, but I 
would consider that to be merely a server implementation detail.)