|
|
03-10-2008
|
|||||
|
|||||
|
Distributed G.C
Does the ice framework provide anything to help identifying and destroying remote objects which are no longer accessible by clients. E.g. a remote object that was returned from a remote method call and was discarded by the caller (or the caller crashed and could not destroy it)?
|
|
03-10-2008
|
||||||
|
||||||
|
No, there is no such mechanism built into Ice. In fact, to the best of my knowledge, there is no reliable and scalable distributed GC in any commercial middleware.
The simplest approach to solve this problem is sessions with associated timeouts. Check Michi's article "The Grim Reaper: Making Objects Meet Their Maker" in issue 3 of our newsletter Connections - http://www.zeroc.com/newsletter/issue3.pdf.
|
 |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Distributed Transaction Architecture | hyuuuu | Help Center | 0 | 11-06-2005 10:10 PM |
| Distributed class instances | hiasl | Help Center | 1 | 08-04-2005 07:56 AM |
| Distributed Data Exchange.. Help! | JaneShang | Help Center | 1 | 04-30-2005 07:15 PM |
| How to handle distributed transactions | robert | Help Center | 3 | 10-31-2004 10:35 PM |
| some design issue on distributed filesystem | soloman817 | Help Center | 1 | 07-13-2004 06:39 PM |
Linear Mode
