[omniORB] serialised calss with java orb

Rainer Frohnhoefer rain_list@arcor.de
Sat Apr 12 00:21:01 2003


Am Freitag, 11.04.03, um 12:21 Uhr (Europe/Berlin) schrieb 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.
>

  ... just going through my copy of the VB4.5 docs gives me:

"Overall, VisiBroker's connection management minimizes the number of 
client connections to the server. In other words there is only one 
connection per server process which is shared. All client requests are 
multiplexed over the same connection, even if they originate from 
different threads. Additionally, released client connections are 
recycled for subsequent reconnects to the same server, eliminating the 
need for clients to incur the overhead of new connections to the 
server.  "

   ... so it looks like VB on the client side only offers multiplexing 
through a single connection :(



  Regards,
	Rainer.