I agree with all your points. I just can add, that if you start using NativeBoost FFI you'll find that it follows _exactly_ the rules which you listed. i dont know much about dolphin, but session awareness is one of the first things which i implemented in NB, because as to me, it is the right way how things should be done.
On 11 May 2012 04:08, Schwab,Wilhelm K <[email protected]> wrote: > It's a nice system - we should take lessons from it where we can. In this > case, they *clearly* have it right. > > > > > ________________________________________ > From: [email protected] > [[email protected]] on behalf of Chris Muller > [[email protected]] > Sent: Thursday, May 10, 2012 8:56 PM > To: [email protected] > Subject: Re: [Pharo-project] Short rant on platforms and sessions > >> Dolphin shows us the correct path: session awareness. The image "wakes up" >> and decides where it is running - the vm can certainly help in Pharo's >> case. External resources are *not* cleared on image save - the image might >> keep running, so why release and reallocate? Finalization is best-effort. >> External resources are cleared just before exiting, but *after* any >> associated image save. When the image wakes, one of its first duties is to >> clear (not release via calls) any external resources, because they are known >> to be garbage at this point. >> >> It works, and works well. > > I don't have experience with Dolphin, but that does sound like a > clever solution to avoiding the release/reallocate burden on image > save (and not exiting).. > > -- Best regards, Igor Stasenko.
