saving an image while serving

hi -

Despite the warnings, I am really interested in sticking to the
simplest way of saving my seaside application data, ie periodically
saving and backuping the image. The seaside book states that

  "saving [the image] while processing http requests is a risk you
  want to avoid."

What is the status on that? Is that something we can fix? I have been
running an image in this mode for a few weeks, with no ill effect so
far, but I have had major problems with old image/vm combinations. So
is this something that might be fixed already?

Also, I recall that Avi had made a number of attempts at having an
image saved in a forked background process, eg

 http://lists.squeakfoundation.org/pipermail/squeak-dev/2005-October/095547.html

did anybody pick up on this, or did anything come out of it?

thanks,
Michal

On Sat, Apr 16, 2011 at 8:23 AM, Michal <[hidden email]> wrote:

> Also, I recall that Avi had made a number of attempts at having an
> image saved in a forked background process, eg
>
>  http://lists.squeakfoundation.org/pipermail/squeak-dev/2005-October/095547.html
>
> did anybody pick up on this, or did anything come out of it?

Yeah, we used that extensively for DabbleDB and it worked great. I
don't remember if we solved the GC issue or if we just lived with it,
though.

Colin