[omniORB] NameServer capacity

[Pletyak Attila]

>    Dealing with that many connections might be trouble enough.
> One way that you can deal with this is by having a layer of proxies
> between the clients and the server. Since calls from the proxy
> boxes to the real server will reuse connections, you can control
> the number of actual server connections (and as a result, control
> server threads) by adding proxies. For that many clients, though,
> you might need quite a few. If this is web stuff, it might be
> natural to have one proxy per web server.  You'll have to build
> the proxies into your design, though, unless you use a different
> ORB with proxy support or decide to build your own generic proxy
> mechanism.
>    Other design choices can help, as well. For example, if you use
> a web server extension with CORBA support instead of CGI, you won't
> have to start a new connection for each new CGI process, so you
> might get away without explicit proxies. A lot depends on how you
> plan to use it.
> 
>                                         Gary Duzan
>                                         Verizon Laboratories

Thank you. Let me ask a question regarding this, as I feel now that I am
not that professional in CORBA.

You are right, we will have CGIs running on different web servers. Is it
enough, then, to have an object on every web server which simply routes
the asks to the correct object in the background, and gives back the
answer of that object? Or something more sophisticated is needed on this
proxy method?

I saw some proxy objects generated in the stubs of omniORB but this
cannot be a compass for me as Duncan mentioned previosly.

TIA

Attila Pletyak
Anemo Ltd.