[omniORB] FW: load balancing?

[Tolar, Richard]

Are there any load balancing features built into OmniOrb?



I would like to be able to start up N instances of my server process,
and have omniNames do a round-robin allocation of messages to those N
servers.



This would allow my client application to be safely insulated from the
server configuration, and I can add server processes as-needed for
performance without impacting the client configuration.



Older posts in the email archive seem to indicate that this is a
"code-your-own" scenario...

Is this still true?



e.g.

http://www.omniorb-support.com/pipermail/omniorb-list/2005-May/026699.ht
ml



http://www.omniorb-support.com/pipermail/omniorb-list/2004-June/025513.h
tml



Thanks,



-R



________________________________

From: Tolar, Richard
Sent: Monday, June 12, 2006 6:33 PM
To: 'omniorb-***@omniorb-support.com'
Subject: load balancing?



Are there any load balancing features built into OmniOrb?



I would like to be able to start up N instances of my server process,
and have omniNames do a round-robin allocation of messages to those N
servers.



This would allow my client application to be safely insulated from the
server configuration, and I can add server processes as-needed for
performance without impacting the client configuration.



Older posts in the email archive seem to indicate that this is a
"code-your-own" scenario...

Is this still true?



e.g.

http://www.omniorb-support.com/pipermail/omniorb-list/2005-May/026699.ht
ml



http://www.omniorb-support.com/pipermail/omniorb-list/2004-June/025513.h
tml



Thanks,



-R

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20060612/340e9f2f/attachment.htm

[Duncan Grisby]

Post by Tolar, Richard
Are there any load balancing features built into OmniOrb?

No.

Post by Tolar, Richard
I would like to be able to start up N instances of my server process,
and have omniNames do a round-robin allocation of messages to those N
servers.

That's not really what the CORBA naming service is for. The naming
service does not allocate messages to services. It merely maps names to
object references.

If all you want is to be able to register references to multiple service
instances, then give them out to clients in a round-robin way, it's
trivial to make your own service that does that, either using the naming
service interfaces, or something simpler.

Cheers,

Duncan.