Modularization of MICO

In iX 10/2000 is mentioned, that the TAO Orb can load Modules like the IIOP over SSL as Shard Library. I think, things like the Security-Service should be one or more such modules, because

there a more than one possibility to solve for example, SSL-Based oder GSSAPI -Based (Kerberos or SESAME) Security-Modules
sometimes one does want a small MICO ...

There is the possibility to load modules over the BOA-Mechanism. But in the Code there must be a ORB::bind .

A good addition could be to specify Moduls other the commandline or the micorc-File like

   -ORBmodSSL_Cert

the Syntax like

   -ORBmod<modulename>[_<parameter>]

in the Mico-lib Directory there could be then a module like

   mod<modulename>.so

In ORB::ORB_init , one could interpret the commandline and the rcfile one time , and

keep a ORB-Property list (the Options now !)
load the modules

The Modulelist should be shared with the BOA-Library-List, so that modules can loaded with the BOA-Library-Aktivation and the preloading.

Test for a shared Module

For a prototype here a test-Module , the insecurity-Service-Module.
There is a InsecurityCurrent and a shared Interceptor and it works :-)

You could download it: sharedintercept.tgz

A few remarks:

the insecurity.idl is compiled with option -pseudo, because we don't need marchalling, because ist is loadet into one addresspace
in the unsinn()-Operation we throw a exception, and it works with linux2.2.16, glibc-2.1.2 and gcc-2.95.1 gnuas, and ld 2.9.5 with BFD 2.9.5.0.24

With the above mechanism, the mico-orb should be modularizable with shared libs...

Informatik- und Netzwerkverein Ravensburg e.V Rudolf Weber