[JDEV] Jabberd in a distributed environment.

[Tony Bamonti]

fyi.....The latest SCM is available at http://scm.jabberstudio.org/


Tony Bamonti
Jabber, Inc.

-----Original Message-----
From: Philippe Raxhon [mailto:raxhonp at easynet.be]
Sent: Friday, September 13, 2002 3:38 PM
To: jdev at jabber.org
Subject: Re: [JDEV] Jabberd in a distributed environment.


Since I didn't see any reply on the list, I'm going to send my 2 cents.

There are 2 java servers I know of:
- a non-free but open-source: 
http://www.alsutton.com/software/jabserv/index.html. Quite basic, not 
really finished. The author provides also some jabber related libraries
- on open-source: http://sourceforge.net/projects/jabaserver/. Not 
finished but more robust, based on the avalon/phoenix framework.

There's also the jabberbeans project 
(http://www.jabberstudio.org/projects/jabberbeans) that provides some 
basic server side code.

I also have just discovered today that marbles ("Java Library that 
provides both primitives and framework for development of Jabber 
services") has reached 1.0 and can be found on http://www.jabber.com/ in 
the developers area. It can be used to write server side components. 
BTW, one can also find there jabber documentation.

For the rest, I remember "of an open-source server-to-server component. 
This "Server Connection Manager" (or SCM) will help build out the Jabber 
network by making it easier for Jabber servers to reliably connect to 
each other" (see http://oid.jabber.org/?oid=2351) but can't find more 
anymore about it.

You can find here an introduction on jabber components: 
http://docs.jabber.org/general/html/component-intro.html

Here more about s2s dialback: 
http://docs.jabber.org/draft-proto/html/dialback.html

Finally, here's the jep on transporting xml-rpc over jabber (delivery of 
commands): http://www.jabber.org/jeps/jep-0009.html

FYI, client information are normally managed by the server they belong 
to. These information can be stored in files, database (mysql, odbc, 
...), ldap. Routing of messages between server is simple, as soon as the 
server has a FQDN. If a client is offline, messages are stored on its 
server.

Cheers

Philippe

Michael Hughes wrote:

> I am interested in using Jabber in a large distributed environment.  I 
> already have a multi-tiered architecture that is used for software 
> delivery and supports a user base of approx. 200,000 users.  It 
> consists of 3 tiers,
> 1 Central server
> 10 2nd tier servers that are located at network access points.  All 
> are hidden behind a single DNS Round Robin.
> 400+ 3rd tier servers that are located at client locations.  User to 
> server ratio is limited to a max of 1000 to 1.  All current clients 
> and servers are wintel, and run JRE 1.3.1.   Servers are a minimum of 
> Dual PIII 500 with 512MB Ram.  In the future clients and servers will 
> also be run on an assortment of unix flavors so Java is an absolute must.
>
> For software distribution, clients contact the 2nd Tier, and are 
> redirected to the best available 3rd tier servers automatically based 
> on network subnet.  This assignment information is stored on the 
> client machine and would be available for my Jabber client.  This 
> being the case, there would be no problem handling the redirection, 
> load balancing, or fail over from the client perspective.  This 
> approach is old hat for us and has proven to be a very reliable 
> approach for gathering data and sending it upstream, or downloading 
> and installing code updates.
>
> What I am contemplating is using Jabber to provide real time presence 
> data, as well as a method for delivery of commands to the remote 
> clients from a central location.  The client portion of this looks 
> very straightforward and I see little problem with coding a client in 
> java to facilitate this portion of the project.
>
> The server portion however does not look so straight forward.  There 
> seems to be no Java based server components other than for web 
> servers. Also there seems to be little information about use of Jabber 
> in a distributed environment such as this.  Thus far I have found 
> little detailed information on server 2 server communications, or how 
> client information is stored, or how the one would go about locating 
> clients that are nested several servers deep.
>
> Any thoughts or feedback on this project would be greatly appreciated.
>
>
> Michael Hughes
>
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>



_______________________________________________
jdev mailing list
jdev at jabber.org
http://mailman.jabber.org/listinfo/jdev