[JDEV] Components ids
David Sutton
jabber at dsutton.legend.uk.com
Mon Nov 11 13:37:33 CST 2002
Hello there,
whatever at jabberserver is reserved for client logins. Components need
their own FQDN, however this doesn't need to be real if only users
who are connected to the local jabber server are to access the
component.
I use *.localhost, just as its clear that only local clients can
connect.
Regards,
David
On Mon, Nov 11, 2002 at 08:11:23PM +0100, Fabio Forno wrote:
> Ulrich Staudinger wrote:
>
> >i assume they just need to be reachable for the server to which a
> >component is connected to. The server then does the routing of packages
> >directed to the component. *not sure about this*
>
> This should work only when clients and components are attached to the
> same server (I've tried with success). But if I want to make a component
> reachable from other servers I think I need to have
> component.jabberserver as alias for the host. It wouldn't be neccessary
> if I could use jids such as component at jabberserver also for components,
> but I haven't figured out wehther it is possible or not.
>
> --
> Fabio Forno - PhD Student
> Politecnico di Torino - Dip. Automatica ed Informatica
> C.so Duca degli Abruzzi 24 - 10129 Torino (Italy)
> Phone: +39 011 546 7137 - JabberId: sciasbat at jabber.linux.it
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
--
David Sutton
Email: dsutton at legend.co.uk
Jabber: peregrine at legend.net.uk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20021111/0fede9e6/attachment-0002.pgp>
More information about the JDev
mailing list