James Mansion wrote:
> Scott Oaks wrote:
>> be faster in that case since it can keep all the connections alive. And
>> a CORBA server with one thread/client couldn't scale fo 10K users at all
>> (unless there's some disconnect/reconnect part of the protocol that I
>> don't know about).
>>
> CORBA is not session based. I believe there is no requirement to keep
> the connection open
> past the return to any in-progress RPC. 10k in-progress RPCs???
There are no such requirements, but many CORBA implementations keep
connections
open for re-use for subsequent invocations. The server is free to close
a connection at any
time so long is there is no pending response on that connection.
Implementations also do create sessions
bound to connections for things like the negotiated codeset and the RMI-IIOP
full value description information. But such sessions are re-created
every time a new
connection is used.
I also do not believe 10K concurrent remote invocations is a likely
scenario for CORBA.
The usage patterns we see are at most a few hundred concurrent invocations.
Ken.