[Seaside] saving an image while serving

Sebastian Sastre sebastian at flowingconcept.com
Sat Apr 16 15:39:53 UTC 2011

Given that you don't need transactions, to make that style work, I suggest this:

1. save the image from time to time (as best suits your needs) like you're doing now
2. use a secondary way to dump the object graph
3. use the normal image for as long as things are good
4. when shit happens you "transplant" the object graph into a new "reincarnation" of your app in a fresh image
5. repeat

For dumping the ODB you have options: image segments, SIXX comes to mind now

If you make for yourself some "rescue" kit (script, tools, preloaded code in fresh image), you can make 4 quite painless (or, why not, monitored and automated)



On Apr 16, 2011, at 12:23 PM, Michal 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20110416/b549184a/attachment.htm

More information about the seaside mailing list