On Sat, 12 Jul 2003, Dawid Szymanski wrote: > Are there any transports that are able to compile againt jabberd2?
All current transports are run as a module within jabberd14 but can connect as a Jabber component to any Jabber server. - why jabberd14 at all then? The transports use some parts of the jabberd14 code (XML parser, Jabber packet libs...). - how do the transports within jabberd14 connect to jabberd2? Via TCP/IP and the connect/accept mechanism. The procedure is the same as with external components and jabberd14. You setup the component with a "small" XML configuration file containing the component/transport's configuration and a service section containing an "<uplink/>" and "<connect>...</connect>" section. This tells the jabberd14 which runs the component to connect via TCP/IP to another Jabber server (which of course has to listen on the selected IP and match passwords). BTW the whole thing is internally and is neither a c2s (client2server) nor a s2s (server2server) connection. Both the documentation for AIM-t and JIT provide further details on the procedure. Regards _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
