I changed the requirement from Module Load to Library Load to more
accuratley describe that this is a dynamic shared library load
capability vs. the module load capability of the likes of Linux, Apache,
etc.
Analysis documents are visible online (follow the requirements links).
I am trying not to encroach on object resolution behavior as abstracted
by CORBA, JNDI, RMI and sticking to an immediate design/implementation
of just a ELF ABI "C" interface capable class by using dlxxxx API.
In the long run we will want to have the framework be able to access the
standard distributed objects (through CORBA, etc.), but I am in the mind
of enabling a more efficient class resolution/access mechanism, possibly
by leveraging the work of the MMXX project
https://sourceforge.net/project/?group_id=4309 , although he seems to
have stoped development for the moment.
Anyone?
--
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package
|
