Chris, I respectfully disagree. I know what you mean about "saving garbage," but after giving it a lot of thought over years of faithful service from Dolphin, I realized that it is a perfectly fine design because it allows objects and external resources to plow merrily past an image save. The bogus data is quickly discarded on startup because it is only then that it can be recognized as garbage.
As for first-class connections, that sounds fine as far as it goes. Who sets policy about timeouts and expected activity levels? I submit that one size does not fit all; Microsoft tried it (DCOM), and it was a _total_ disaster. Provide all the slick stuff you want, but we should also grant our peers (developers) access to working sockets, and having them cut off on snapshots just because "Squeak does it that way" is not the way to meet Pharo's mission. Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Chris Muller Sent: Friday, August 28, 2009 10:21 AM To: [email protected] Subject: Re: [Pharo-project] Startup/shutdown shutDown: already provides a boolean indicating whether a quit is about to occur or not. I suppose any code is welcome not to cleanUp properly if it's not a quitting situation.. What feels wrong to me would be to save "garbage" (what will be unusable sockets, etc.) into the saved image. > occurance would clobber all sockets, all web users, all database > connections, Which is why first-class connections / sockets should be used, which don't depend on their underlying physical socket to be always connected. This is what Magma does. A socket can get disconnected at any time for a variety of reasons, not just an image save/shutdown. I think the software should, transparently to the user, reestablish connections lazily, making saving the image a non-issue. - Chris _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
