[Seaside] saving an image while serving

[Norbert Hartl]

Am 18.04.2011 um 00:02 schrieb Nevin Pratt:

> 
> Nevin
> 
> 
>> Nevin,
>> 
>> without giving away any confidential information can you elaborate a little on how you do things? That might be a good scenario for people to know not to care about persistence and scalibility to early.
>> I have problems digest what you are saying. Thinking of a single image it can only work if you can have the complete model in memory without problems. Or do you do domain partionioning? It would be interesting to know your approach.
> 
> You are thinking about it too hard.
> 
> Just an image.  Nothing fancy.  Everything in memory.  No problem.  Really.
> 
No, I don't think I'm making it harder. It is just that I cannot understand your setup.
> 
>> Second I would like to know how you replay data after a crash. A plain image approach wouldn't help because there is no persitence at all and the data would be lost. Do you replay from another server/system or do you store anything outside the image for error recovery?
>> 
>> 
> 
> Again, you are thinking about it too hard.
> 
> The "plain image approach" works just fine.
> 
>> and the data would be lost. 
> 
> So what.  Grab yesterday's image.  Put the data back in since yesterday.
> 
> Just an image.  Nothing fancy.  Everything in memory.  No problem.  Really.
> 
> Nevin
> 
Ok, that seems to make things more clear. If you say "Put the data back in since yesterday" than it means to me the data is not created by the image just served. My point was that in a common scenario the data is created in the image and if you don't store it anywhere you simply loose it. No chance to replay. But in this case your scenario is of course easy to do. You never have much difficulties if you don't need to care about persistence. If you need to the statement "...just a plain image.." is not of any help.

Norbert