Hello there, whatever@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@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: [EMAIL PROTECTED] > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev -- David Sutton Email: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED]
msg07668/pgp00000.pgp
Description: PGP signature
