[Seaside] non-blocking call:

Lukas Renggli renggli at gmail.com
Sun Jul 8 19:58:03 UTC 2007

> > Good to know. So this is only working inside the render loop, right?
> Yes.

I would rather say from within callbacks or WATask>>#go (which is
internally implemented as a callback).

> > So I have to find a way to setup the components in initialRequest:
> > and let them be display inside the render loop.

The question is, if you really want it to block in #initialRequest:?
That could have very strange side-effects where some components
already received #initialRequest: while others didn't.

> The usual trick is to use a WATask and do the #call: there in #go. You
> have just found one of the weaker points of Seaside REST support. This
> might be something for 2.9.

I don't see a problem there. Use #show: in these cases, to make the
non-blocking behavior explicit.


Lukas Renggli

More information about the Seaside mailing list