[Seaside] non-blocking call:

Norbert Hartl norbert at hartl.name
Mon Jul 9 06:56:52 UTC 2007

On Sun, 2007-07-08 at 21:58 +0200, Lukas Renggli wrote:
> > > 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.
Now I got it. It is even better than before. I have a WATask which
delegates the action to my Action classes. I do a show: aTask in
initialRequest: and in go the delegation occurrs. And it seems it
solves also one or two of my other problems.

thanks to both of you. You do a great job!


More information about the Seaside mailing list