[omniORB] ETS Kernel: Naming Service as part of an application?

[Helge Penne]

The PharLap ETS Kernel only supports a single application per system.
This makes it difficult to use the Naming Service on a network that
consists only of ETS Kernel based nodes, as the Naming Service would
seem to require a node of its own.

Is it easy to integrate the Naming Service code into an application
(running as a thread in a larger application)?  Has anybody tried this?
Will it have any requirements with regards to thread priority?  Ideally
it should run as a low priority thread, to avoid blocking the "real
application"...

I'll be grateful for any relevant input on these issues.

--
Helge Penne (helge.penne@datarespons.no)
Senior Software Development Engineer
Data Respons AS, Postboks 489, N-1323 Høvik, Norway
Phone: +47 67112081 / 22719957 (work/home)