[omniORB] omniNames memory leak (sorta)

[Gary D. Duzan]

   What would probably be more useful is a tool to search OmniNames
for (locally) unreferenced contexts, examine their contents, if
any, and let you delete them manually, if desired. Doing distributed
garbage collection in CORBA isn't practical without designing it
into the system, as is generally accepted in the CORBA community.
For details, see the "Pacific Ocean Problem" in Henning & Vinoski's
"Advanced CORBA Programming with C++".

					Gary Duzan
					GTE Laboratories



In Message <Pine.LNX.4.04.9911010654110.22106-100000@disks.tcnet.eu.org> ,
   Michael Loftis <zop12@mindless.com> wrote:

=>
=>
=>On 1 Nov 1999, Tristan Richardson wrote:
=>
=>> Michael Loftis <zop12@mindless.com> writes:
=>> 
=>> As far as I understand it this is the correct behaviour.  Just because a
=>> context is unbound doesn't mean some client doesn't have a reference to
=>> it, and is about to rebind it somewhere else.  However, practically
=>> speaking it would be nice if there was a way to automatically clean up
=>> such orphaned contexts.
=>
=>Maybe that's a project for me....  It seems simple enough, but then again
=>so does everything until one does anything about it.  I suppose what will
=>need to be done is implement some sort of reference count checking
=>mechanism before an object gets deleted.
=>
=>:shrug:
=>
=>Then again I'm still much too fuzzy on the ORB internal workings to be
=>sure that'd work properly.
=>
=>
=>
=>