Implementation Repository

Originally posted to the other mailing list by
mistake...

Will be posting some extra stuff soon; looks like
there's been a lot of progress here lately, and I'm
coming in a little bit late. I am hoping the work I've
done may be of some help!

 --- James Waller <[email protected]> wrote: >
Date: Wed, 29 Jan 2003 23:56:36 +0000 (GMT)
> From: James Waller <[email protected]>
> Subject: Implementation Repository
> To: [email protected]
> 
> Hello,
> 
> First I'd like to apologise for waiting until now
> before posting anything on this subject. I was
> unable
> to discover the recent interest on this topic until
> now because I've been without an internet connection
> for the first half of this month!
> 
> I'm very interested in joining this discussion as I
> have been working on an Implementation Repository
> for
> omniORB for almost 3 months now. It is nearly at the
> point where it is usable; a working ImR daemon and
> server interface library are just around the corner
> (about two or three weeks before I have some code to
> demonstrate). I intend to add an administration tool
> as well. It only compiles on Linux at present and
> its
> makefiles are independent of the autoconf system.
> 
> This ImR works in a very similar way to the one
> described in the Henning paper and the "Advanced
> CORBA
> Programming with C++" book. Server programs are
> registered with the ImR by name, then one or more
> POAs
> are registered with the ImR for each server. Any
> object references created in those POAs at the
> server
> are translated to references to the ImR. Each server
> has configurable parameters such as command-line
> arguments, activation mode, user, group and so on;
> calls are present in the ImR interface for accessing
> this information.
> 
> When a server starts up, it makes a call to the ImR
> to
> notify the ImR of its availability. A "manager"
> object
> is created in the ImR for each server with a
> corresponding proxy object in the server itself,
> provided by the server interface library. The
> manager
> object is responsible for sending "ping" requests to
> the server (to check if it is still alive at certain
> points) and sending instructions telling servers to
> terminate themselves in an orderly fashion. The
> corresponding proxy object receives these requests
> and
> deals with them in the appropriate way.
> 
> I will send some IDL in my next posting; is it okay
> to
> attach files to mailing list posts?
> 
> Cheers,
> James Waller
> 
> __________________________________________________
> Do You Yahoo!?
> Everything you'll ever need on one web page
> from News and Sport to Email and Music Charts
> http://uk.my.yahoo.com
>  

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com