[JDEV] Components ids

[Matthew A. Miller]

All of the jabber server implementations [I am familiar with] externally
treat components' JIDs (almost) as if they are jabber servers. So, your
component must have a Fully-Qualified Domain Name (FQDN) as its JID, and
that FQDN needs to resolve via DNS to the jabber server running the
component.

The solutions given up to this point are valid if only users on your
server will be accessing the component.  If the component is to be
accessible to users outside of your server, the above is what needs to
be done.

Alternatively, you *could* write your component to connect as a client
(to get a JID such as "component at server").  This means your component is
really a client though, with all the benefits, restrictions, and
overhead that entails.


Hope this helps,

Matt


On Mon, 2002-11-11 at 11:11, 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.
-- 

Matt "linuxwolf" Miller
JID:	linuxwolf at outer-planes.net
E-MAIL:	linuxwolf at outer-planes.net

- Got "JABBER"? (http://www.jabber.org/)