Yes, but why 32MB? -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Marcus Denker Sent: Sunday, November 29, 2009 12:18 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Method versioning in Pharo images On Nov 29, 2009, at 6:15 PM, Schwab,Wilhelm K wrote:
However, for "independent" read "redundant." Take away the redundancy, and there is a single point of failure. That keeps surfacing as a good idea, and I fear the backlash once the redundancy gets removed in the name of saving space.
but if you want redunancy, provide a service that does that. One thing. And than reuse it. A log of course would provide redundancy. That's the definition. The only difference is that it would *only be a log*, and nothing else.
What is the source of the change log size limit?
32MB. Marcus _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project