[omniORB] Thread and connection policy for very large configurations

[Serguei Kolos]

Hi

I 'am thinking of using the omniORB for my project, but there is one point
I want to understand.
I have to implement a CORBA server which is able to handle 2000 concurrent
clients with each client sending short request to this server once per 
second.
What thread (or connection) model I should use to have efficient 
implementation???
On one hand it's relatively clear that the most suitable one is the 
ThreadPool.
Fine, but what about number of simultaneous connections? Closing and opening
connection each second for each clients will kill my server. On the 
other hand,
as far as I know, the omniORB use internally the select system call 
which does not
work with socket id > 1024 (without recompilation of the OS kernel). So 
that my
server can not keep all the connections open simultaneously.
Could anyone advice me what I can do in this situation?
By the way, don't you think that using the poll instead of the select in 
the omniORB core
might be a good idea? Poll has the same efficiency and overhead as 
select but does not
have the 1024 limitation.

Cheers,
Sergei