[omniORB] educate me ...

[Richard Hardgrave]

Hi,
	I'm still at the investigation stages of finding a
replacement for Orbix in our system. We're currently only
using CORBA between a C++ process (client) and the CLIPS
(Lisp-based production system)(servant).  We do not yet
use CORBA for our networking mechanisms.  BTW, the
production system is NOT re-entrant code, so we generally
have a whole flock of servants waiting around to service
test requests.

	Orbix appears to use this "orbixd" daemon for both
object activation and managing the Implementation Repository.
The omniORB 3.0.3 is just a shared library, correct?  I can
see omniNames sitting around, waiting for requests, but the
omniORB is not an independent process or daemon, right? What
occasionally makes me pause is the mention of the "runtime ORB".
What sort of distinction is the author trying to make with
"runtime"?

Regards,

Richard Hardgrave