[jdev] client vs component

Jacek Konieczny jajcus at bnet.pl
Fri Feb 20 02:01:49 CST 2004

On Fri, Feb 20, 2004 at 06:50:11AM +0300, Alexey Nezhdanov wrote:
> >3. I need the kind of flexibility that will allow this architecture to 
> >scale (i.e. so I can have several external standalone apps that basically 
> >listen for the same messages and process them as they come in.)
> AFAIK there are no balancing mechanisms in jabber server so you will to 
> write them yourself

I think this could be easily done with presence priorities when
application is implemented as client. Each application instance would
log in to the same Jabber account, but with different resource. And they
would change their presence prioties according to their current
resources and load. The Jabber server would send messages always to the
instance with highest priority. This is simple and not perfect load
balancing solution, but may be good enough in many cases.

Other solution would be to make some kind of message multiplexer - it
could be a component or a client.


More information about the JDev mailing list