[Vm-dev] [squeak-dev] Image Segment semantics and weakness

Mariano Martinez Peck marianopeck at gmail.com
Wed Oct 22 15:32:06 UTC 2014

On Wed, Oct 22, 2014 at 2:05 AM, Bert Freudenberg <bert at freudenbergs.de>

> On 20.10.2014, at 18:55, Mariano Martinez Peck <marianopeck at gmail.com>
> wrote:
> > The few users I found, were NOT using the real purpose of ImageSegment,
> that is, object swapping. It was used instead as an object serializer. For
> that, they use #writeForExportOn: which ended up using SmartRefStream for
> the rest of the objects.
> Well, if you look closer, you will see that projects use image segments in
> two completely different ways. One is, as you say, for serialization, which
> is not the best use of image segments, agreed, especially with all the
> other logic wrapped around it.
> But if you enable projectsSentToDisk then entering a project will swap the
> previous project to disk as an image segment, allowing you to have images
> with very large projects without having to hold all in main memory at the
> same time.
> This uses a completely different code path and file format than regular
> project export. The same technique could be used to swap out arbitrary
> chunks of an image.
Totally agree.  So it seems we agree that the key and good part of
ImageSegment is that one, swapping out, but not as a general object graph

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20141022/f8d56737/attachment.htm

More information about the Vm-dev mailing list