[JDEV] transport problems
dwaite at jabber.com
Fri Oct 27 14:26:37 CDT 2000
Brian Lalor wrote:
> On Fri, 27 Oct 2000, Erich Zigler wrote:
> > On Fri, Oct 27, 2000 at 11:32:18AM -0400, Brian Lalor wrote:
> > > > 2.) Do you want to use jabber.org's transports or are you installing your
> > > > own?
> > > Can you do this without specifically configuring jabber.org to allow it?
> > Yes, but this is a one shot deal. If you decide sometime in the future to
> > use your own transports the transition is not an easy one.
> Does my server have to be accessible to the rest of the world in order for
> this to work? Will my server keep the connection to aim.jabber.org open,
> or will aim.jabber.org have to open a new connection periodically to my
> server (which is behind a firewall)?
It is not recommended that the jabber.org transports be used for anything beyond
test servers, as jabber.org is already a development (beta-stability) server, and
That said, transports with valid DNS entries are externally available, while if
the transport is run by the Jabber server and not externally accessable, the name
does *not* necessarily need to be valid in DNS.
> I just tried this, but my client (Gabber) presented an empty agent
> registration dialog.
without seeing the resulting XML, this could either be a problem with the
connection between servers, or a downed transport (again, jabber.org is a
> In general, what's the Jabber protocol say about intranet servers? I
> think that, as a client of an internal server, I should be able to add
> people to my roster who are on an external Jabber server, but if I
> understand correctly now, that's not possible. You'd almost need a
> jabber-to-jabber transport...
If it is a completely intranet server, it does not need a connection to the
outside world - just remove mod_update(?) so that it doesn't try to search for new
server versions with jabber.org.
However, if you want to communicate with outside domains, the server does need to
be accessable from the outside, so remote messages come in. As far as I know, the
server connection is supposed to be long-lived, but definately not immortal.
More information about the JDev