In the open source jabber server architecture, each component needs to deal
with a full domain name. With our instant messaging architecture (TIMP)
instead, you can plug different components on the same domain (so why we
call them plugins), still preserving the performance advantages of
components; maybe on the upcoming newer jabber releases and with other
jabber component libraries you can make even much more complicated component
addressing tecnique (e.g. based on XPaths): so it is not right to say that
components needs to be mapped to a full domain, while instead it is more
precise to say that the Jabber Reference implementation supports only this
kind of components (with its "built-in" API, you can always extend it
somehow to implement you component framework).

Regards,
   Francesco Delfino
   Tipic Inc.
   http://www.tipic.com
   e-mail & Jabber: [EMAIL PROTECTED]
   blog: http://www.tipic.com/blog/pluto@;tipic.com


"Fabio Forno" <[EMAIL PROTECTED]> wrote in message
news:3DD000DB.70808@;kamin.polito.it...
> 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]


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.408 / Virus Database: 230 - Release Date: 24/10/2002




_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev

Reply via email to