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

[Richard Dobson]

> Thanks for the bug report. We've now fixed the category and type (bug
> fix will be in next release). The name is now "Jive Messenger Server" by
> default, but that default can be changed by editing a configuration
> file.

You are welcome ;)

> Yep, same issue -- http://www.jivesoftware.org/issues/browse/JM-407.
> We've implemented a fix and will hopefully roll it out to the server
> later today.

Cool good good.

> This general subdomain issue was actually a really interesting one for
> us when implementing s2s. One thing I find frustrating is that DNS
> entries have to be made in order to get s2s sub-domains to work with
> most servers. That's a bummer for things like MUC, where server admins
> might not have easy access to DNS but still want the service. So, the
> algorithm we use is to examine the server domain and attempt connections
> to the subdomain tree in order. So, if connecting from another JM server
> to conference.foo.jivesoftware.com:

>  1) Try s2s connection to conference.foo.jivesoftware.com. If that
> fails:
>  2) Try connection to foo.jivesoftware.com. If that fails:
>  3) Try connection to jivesoftware.com.

> So, let's say that your XMPP server is actually foo.jivesoftware.com. In
> that case, conference.foo.jivesoftware.com will still work from the
> other JM server even if you don't have DNS setup for conference.foo.

Interesting solution but not exactly standard, and will only work between 
servers that are running Jive Messenger, according to the specs for s2s the 
fact that the MUC service is a subdomain of another server is irrelivant, 
its not the root domain that the other servers are trying to talk to its the 
conference service itself directly, thus the need to have the DNS records 
setup correctly so that they can even see if it exists, I would suggest that 
if your users dont have access to add DNS records for subdomains then they 
either obtain that access or simply purchase a new domain for their MUC 
service to be known as e.g. conference-jivesoftware.com, whether the MUC 
service is known as conference.jivesoftware.com or 
conference-jivesoftware.com should make no difference.

Richard