[Seaside] non-blocking call:
philippe.marschall at gmail.com
Sun Jul 8 19:39:14 UTC 2007
2007/7/8, Norbert Hartl <norbert at hartl.name>:
> On Sun, 2007-07-08 at 20:39 +0200, Philippe Marschall wrote:
> > 2007/7/8, Norbert Hartl <norbert at hartl.name>:
> > > Hi,
> > >
> > > call: should be blocking, right?
> > Yes.
> > > Does it block under
> > > any circumstances?
> > No.
> > > I have a component where the call:
> > > is non-blocking. It just executes the statement after
> > > the call: immediately.
> > One place where it doesn't block (and doesn't work) is in #initialRequest:
> Ok, that's the point. It is code invoked from initialRequest:
> Good to know. So this is only working inside the render loop, right?
> So I have to find a way to setup the components in initialRequest:
> and let them be display inside the render loop.
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.
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the Seaside