[Seaside] Re: Render loop... not looping
Esteban A. Maringolo
emaringolo at gmail.com
Tue Nov 8 20:40:17 CET 2005
2005/11/8, Julian Fitzell <julian at beta4.com>:
> Esteban A. Maringolo wrote:
> > Julian Fitzell escribió:
> > And what is the purpose of the critical:ifError: method?
> > Why it uses a mutex and forks the evaluation of the block?
>
> It's designed to ensure that only one request is evaluating within a
> session at a time. This is desirable because otherwise everything would
> need to be written to support concurrency. In fact, given that we are
> reverting object instvars back and forth to handle continuations this is
> pretty important even at the system level. As it stands, that semaphore
> ensures you only need to worry about concurrent access of resources that
> are accessed by more than one session (db, etc).
Thanks. I've imagined it to be that. What I didn't see is the side
effect of not having to deal with concurrency everywhere.
By now I'm using it without mutex nor semaphore until I find a
solution to make it work on Dolphin.
Any clues about why it doesn't render again?
--
Esteban A. Maringolo
eMaringolo at gmail.com
More information about the Seaside
mailing list