[JDEV] Transports new approach

[Keith Minkler]

Dennis, et al..

the reason that didn't work by the way, is becuase the id is a routable name within jabberd...

so when you had the two "linking" instances (connect on one, and accept on the other) the original jabberd sending to myinstance sends it to the connect instance, delilvering it to the other jabberd.  now, when the other jabberd gets the packet, it calls deliver() on it, to get it to where it needs to go... deliver() sees the myinstance (the linker) id, and delivers to that, as any other hostname.. it probably ALSO got delivered to your <host>myinstnace</host> as you would have expected.

the reason scheulyer's (hopes he spells it right) config works, is becuase he used an id that no packets would try to deliver to for the linker instances... (i.e. mylinker) (note also that this must be the SAME id on both the connect and accept instances -- due to the way base_accept handles ocnnections)  also, you need to include <host/> sections for *every* host that is on the *other* side of the linker.

you can link multiple jabberds together, such as:

A <--> B <--> C

A & B would have a AB_linker instance, and B & C would have a BC_linker...

the linker on A would have to have <host/>s for all this hosts in B and C

the linker AB_linker on B needs the <host/>s for A and the BC_linkekr on B needs the <host/>s for C

the BC_linker on C needs the <host/>s for both A and B listed.

Hope this example makes sence, and helps clarify the jabberd linking..

(note that you can also link jabberd's with exec and stdout)
such as:

... in the parent jabberd config ...

<service id="linker">
  <exec>jabberd -c linker.xml</exec>
</service>

... and in the linker.xml ...

<service id="linker">
  <stdout/>
  <host/>
</service>


Hope this helps!
Keith Minkler

On Tue, Dec 12, 2000 at 07:32:19PM +0200, Dennis Noordsij wrote:
> On Tuesday 12 December 2000 19:26, Thomas Charron wrote:
> > From: "Dennis Noordsij" <dennis.noordsij at wiral.com>
> > Subject: [JDEV] Transports new approach
> >
> > > <service id="myinstance">
> > >  <host/>
> > >  <connect>
> > >     ....
> > >  </connect>
> > >  <load><runcomponent>./src/component.so</runcomponent></load>
> > > </service>
> >
> > Eww.  I don't think one instance of a service can be connected *BOTH* as a
> > loadable module AND a remote connection.  You'd need a second, distinct,
> > service ID for the second service.
> 
> Yes, tried that, makes sense, but didn't work either :-)
> 
> I am very much open to any configuration that will let me do what I wanted, 
> no matter what, so feel free! :))
> 
> Regards,
> Dennis
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev