[Seaside] saving an image while serving

[Robert Sirois]

It's not really something to be fixed. It's more of a short term solution. That being said, Avi Bryant built DabbleDB based on image persistency.. basically (as I understand it) he created a minimal image for each project on there and just saved the data in that image.

GemStone does this (essentially), too, but with all the facilities a database should have. There's sandstonestone db (with the GOODS backend). You can get mysql drivers from squeaksource (not too bad to set up). There's a lot of persistency options.

Sent from my G2
RS

Michal <michal-list at auf.net> wrote:

>
>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
>_______________________________________________
>seaside mailing list
>seaside at lists.squeakfoundation.org
>http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>