[omniORB] Visibroker osagent as naming service for omniORB po ssible?

[Ivanov, Roumen]

Only about the second question.
We had similar situation here. We are running omniNames 3.0.2. When many
clients try to connect almost simultaneously (average - 40 per sec.), the
naming service either dies or gets deadlocked. Looking for a quick solution,
we had to extend the reconnect interval limits x 10 in order to keep the NS
alive. This might be not the case with other versions or implementations
though.

Roumen

-----Original Message-----
From:	Daniel Weber [SMTP:dweber1@austin.rr.com]
Sent:	Saturday, August 04, 2001 03:45
To:	omniorb-list@uk.research.att.com
Subject:	[omniORB] Visibroker osagent as naming service for omniORB
possible?

I'm interested in using omniORBpy to write a script for a system that uses 
Visibroker 3.3.  This system uses osagent and BOA to bind object references.

Does anyone know if it is possible for omniORB to use this as well?

Another question - in  a conversation with another engineer he mentioned
that 
using a name server resulted in excessive network traffic and was not useful

for the number of objects they were using.  They're using under 1,000 
objects, though I don't know the actual number.  I was under the impression 
that a name server could handle this kind of load easily.  Any comments?

daniel