[jdev] Component, Gateway or S2S?

[Daniel Tietze]

Hi.

Thanks for your fast response.

Richard Dobson wrote:
> I would say S2S is the best option for you, otherwise component mode is
> possible but it requires you to run a jabber server along with each copy of
> your server and that it be setup appropriately.

Yes, I figured that out a couple of minutes ago as well.

> So if you are planning to
> deploy this to all your customer sites then I would definately recommend
> taking the extra effort to go the S2S route rather than the easier component
> route, otherwise it will look a bit strange to your users that they have to
> run a jabber server along site your server software.

You're absolutely right - that would be a strange
requirement. A bit like having to set up multiple
telephone switches just to be able to call to
the US *and* Germany :-)

Which sort of brings me to the conclusion that
we'd have only JSO to build on since there
appears to be no other Java library supporting the
server namespace (or - probably better - we could
contribute that part to one of the existing
Java libraries out there).

Is S2S sufficiently supported and accepted in
today's deployed servers, so that it's something
we can actually expect to work? I want to add
something that works and that people can really
use, not just support another buzz-word.

Daniel.