From: Laurent Julliard Date: 2004-11-21T21:51:31+09:00 Subject: Re: Inner Class Relationship James Edward Gray II wrote: > On Nov 20, 2004, at 5:55 PM, Francis Hwang wrote: > >> Since you haven't said much about how you're using this, maybe my >> answer will be a little presumptive, but: Is there are a particular >> reason you want the inner class to relate to the outer class this way? > > > Yes. > > Even if I separate the two classes, my questions remain unchanged: > What's a good way to allow one type of object to send private-ish > messages to another type of object? > > As for details: My outer class is a server. My inner class is a > connection for that server. When a connection ends, I need a way to > notify the Server object to remove it from it's maintenance list. > That's the message I'm wanting to hide from the outside world. > > Thanks for the suggestions. > > James Edward Gray II > > > James, What you need is FreeBase. FreeBAse is a databus written by Rich Kilmer that we extensively use in the FreeRIDE project (Ruby IDE). It allows any Ruby object to publish nodes in a tree -like hierarchy and other Ruby object to listen to what's happening to these nodes. It's a sort of a meeting point for Roby object doesn't know or doesn't want to know about each other. You can get Freebase from the FreeRIDE source code. It's a self contain piece of code that we haven't touched for moths so it is farly stable. The source file is at: http://rubyforge.org/frs/download.php/1641/freeride-0.8.0.tar.gz extract it and take the freebase directory from there. I have cc'ed Rich Kilmer as I know he was thinking of packaging Freebase separately but I could not find it. Laurent