[omniORB] Implementation Repository

[Thomas Lockhart]

Some additional comments on directory structure and build environment:

o autoconf (for the platforms which support it) can be used for this 
package. The config/ directory would conventionally contain autoconf 
macro files, so perhaps the omniImR.conf file can live somewhere else?

o As autoconf is integrated, the package would be configurable to look 
for an existing omniORB installation, just as is currently done with 
omniORBpy. autoconf supports having separate but cooperating configure 
scripts in child directories. So we can put in autoconf support in the 
standalone tarball, and carry it forward if omniImR is moved into the 
omniORB tree later on.

o common/, daemon/, and imradmin/ contain both header files and cc 
files. There is also an include/ directory which contains only a single 
header file. Should the includes be consolidated into the include/ 
directory? Especially if there may be other products (e.g. a server-side 
python layer) which need to see some of the header files to be built.

o If the "common" code is not yet built into a shared library, we will 
want to move toward that. What would the library be called? Something 
like "libomniImR.so"? Perhaps common/ could become src/lib/ (or ??) in 
this tree? And the shared library could be built into lib/ ?

                     - Tom