[jdev] [ANN] Google Talk engineering manager live chat

[Richard Dobson]

> Richard, I have to say I agree with Jive on this one.  Not because I
> disagree with your SMTP and HTTP examples, they are flawless.  The
> issue I have encountered myself is simply that it didn't make sense to
> me to have a different domain name for every service on a server.  I
> was assuming all along that this was a design decision (or flaw) of
> jabberd1 to be honest, not a requirement of XMPP.  After all, you can
> certainly run an SMTP and HTTP server and a million others all on the
> same server using the same domain name.

But you cant, if you are comparing apples to apples then no you cant run two 
entirely different SMTP servers on the same domain name without encountering 
problems, yes you can run and SMTP server and a HTTP server on the same 
domain, but the same goes for being able to run an XMPP server and an HTTP 
or SMTP server, the reason you can do this is because they use different 
protocols on the different ports.

>  Jabber is the only software
> that I have heard of that breaks pieces out this way.

Not really, if you use the example of SMTP you cant run two entirely 
different email services on the same domain.

> When I was first messing with jabber several years ago, it was to
> setup a workgroup server in my large enterprise.  It took me some time
> to realize that those extra subdomains were really required, not
> suggested.  IIRC I actually faked them with local host file entries
> during my experimentation.  It was easier to do that than wade the
> bottomless pit that is IT support.

Sure but once you come to officially deploying after you have stabilised it 
whats the problem with getting the DNS entries setup? Yea if you are in a 
large company you might have to go through some effort getting them setup, 
but those processes will have been defined for a reason, if you are in a 
company you have to control updates to the DNS you cant just let anyone 
change stuff willy nilly, you would have anarchy.

> So what I'm saying is all of your problems raised above would not be
> problems if everything could be done on one domain name.  Wow, Jive is
> giving me that.

But its not, the services are on their own domains, but that is one solution 
to this problem, simply implement the server so that everything appears on 
the same domain name, you are more likely to get overlaps of JID username 
parts when all users and conference rooms etc are all running from the same 
domain name, but its an entirely workable solution, e.g.

User
user1 at example.com

Room
room1 at example.com

or you could diferentiate rooms by preappending them with something to make 
them more unique e.g.

room-jdev at example.com

Richard