[omniORB] Visibroker osagent as naming service for omniORB possible?

[Glenn A. Hochberg]

Visibroker's osagent uses a proprietary protocol--not at all standard, so omniORB
wouldn't be able to use osagent.
If I'm remembering correctly, Visibroker 3.3 came with a naming service as well
that could optionally be used--you might consider using this or else omniNames.

On the load question, I don't think the number of objects per se is the key
criteria, rather it's the frequency of calls to the naming service.  However,
typically if you have large numbers of objects you would only use the naming
service for a few "well known" objects, such as object factories, and get the
references to specific fine-grained objects from the corresponding factory
object.

    -Glenn

Daniel Weber wrote:

> 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

--
Glenn A. Hochberg     | "Any activity becomes creative when the doer
AT&T Labs             |  cares about doing it right, or doing it better."
gah@research.att.com  |      -John Updike
(973) 236-6638        |