[jdev] Component, Gateway or S2S?

[Peter Saint-Andre]

I think the way to go is to build server-to-server connectivity between
instances of your EIM application and domains on the XMPP network.

For Java, I would think JSO is your best bet:

http://jso.jabberstudio.org/

Peter

On Wed, Mar 17, 2004 at 11:14:19AM +0100, Daniel Tietze wrote:
> Hi, all.
> 
> I am currently looking to add XMPP connectivity to
> our (proprietary) EIM application. Specifically, I
> want to add an extension to our IM server allowing
> users of our IM client to communicate with users
> in the Jabber/XMPP world.
> 
> For a number of reasons, I do *not* want to add
> support for connecting to our EIM server using
> any Jabber-compliant client.
> 
> I realize that what I would need to do is announce
> users of our EIM service to the XMPP world and
> deliver presence and message packets to XMPP-based
> clients via a connection to some XMPP server.
> 
> What would be the "correct" way of designing this?
> Would I be developing a "component" (i.e. using
> the "jabber:component" namespace to talk to the
> XMPP server), or would I rather be looking at
> Server-to-server support (the "jabber:server"
> namespace)? Is S2S actually supported in current
> XMPP servers or would I be limiting myself by
> doing it this way?
> 
> I guess I *could* also use "jabber:client" and have
> our IM server masquerade as X number of clients,
> but somehow that does not appear to be the cleanest
> (and most resource-saving) approach.
> 
> Our IM system is 100% Java - is there a Java library
> (LGPL, or commercially licensed/licensable) that could
> get us nearer towards our goal?
> 
> I'd appreciate any helpful pointers on this issue.
> 
> Best regards,
> 
> 	Daniel
>