[omniORB] serialised calss with java orb

[Duncan Grisby]

On Thursday 10 April, Heinrich Goetzger wrote:

> Is it correct, that using omniORB 3.x would not enable to use a
> multithreaded java client (with visibroker 4.5.1)
> to get the method calls from different client threads in different server
> threads on the server side?

It depends on how VisiBroker multiplexes calls from multi-threaded
clients. If it opens a new TCP connection for each concurrent call,
omniORB 3 will dispatch the calls to separate threads. If it
multiplexes the calls on a single connection, omniORB will serialise
them.

The built-in Java ORB always multiplexes on a single connection;
omniORB 3 always opens separate connections; omniORB 4 lets you choose
either.

> But using omniORB 4.x would enable this scenario.

Yes. omniORB 4 does dispatch multiplexed calls to separate threads, so
regardless of how VisiBroker works, you will get multiple threads on
the server. Note that this is not what Rainer called "thread per
call"; it uses a thread pool.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan@grisby.org     --
   -- http://www.grisby.org --