[Seaside] saving an image while serving

[Norbert Hartl]

Am 18.04.2011 um 19:50 schrieb Sebastian Sastre:

> Yes because we couldn't sleep if it wasn't scalable like hell yah! by design :)
> 
> 
Sebastian,

I think you made it bigger then it was intended by anyone. I was just saying that the proposed solution cannot work without keeping external state. An email account with prepared emails is equivalent to a replay log. So you have snapshots and replay logs. That not only makes it a database (an email account is one) but one with a solid approach. I'm glad Nevin clarified it so everybody can see how simple a smart solution can be.

To assume things is one choice. To explain it is a better one. At least in my opinion.

Norbert

> On Apr 18, 2011, at 2:26 PM, Nevin Pratt wrote:
> 
>> 
>>> Not working the way Nevin does. But that's not the Nevin's case. He's saying this "yes is one image, yes if it crashes we need to rollback, yes that architecture doesn't scale horizontally so what? is enough for the business it get us there just fine." (Nevin please correct me if I'm wrong)
>>> 
>> 
>> You are exactly right.
>> 
>> And for Seaside, I don't think our case is very unique.
>> 
>> Your case sounds quite a bit different, though.
>> 
>> Nevin
>> 
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> 
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside