[Seaside-dev] Re: partial continuation implementation

[Julian Fitzell]

On Wed, Feb 4, 2009 at 3:37 PM, Lukas Renggli <renggli at gmail.com> wrote:

> On Wed, Feb 4, 2009 at 1:42 PM, Julian Fitzell <jfitzell at gmail.com> wrote:
> > And on a related note (not to distract from the original question), I
> don't
> > think WAPartialContinuation is as flexible as I would like; it's not
> quite
> > the power tool it could be.
>
> We do not provide power tools for stack manipulation, co-routines,
> continuations, subcomputations, f-operators, ... Seaside is a web
> framework and it should concentrate on the web framework things only.


It's not useful to talk about what we don't provide here. We *do* provide an
implementation of continuations and the current implementation is very
geared to a specific way of implementing Flow. I would like to be able to
experiment with the way we use it and currently it seems unnecessarily
restrictive. There's absolutely no reason to hard-code the marker in the
continuation - that is mixing the implementation of #answer: with the
implementation of partial continuations. Can you give me some reason why it
needs to be there?

>
> We do not even mention continuations on the website. I believe this to
> be vital for Seaside, because continuations are just an implementation
> detail and considered to be scary and incomprehensible by the majority
> of people.
>

That's fine. Nobody said we had to mention it on the website.

>
> Now, if there are bugs in our specific continuation implementation
> these should be obviously fixed in place. Please do not create a
> continuation framework that can be reconfigured to solve all possible
> problems of the world as well.
>

I don't want a continuation framework. I want a continuation implementation
that isn't implemented only to work in the current implementation of Flow.
Particularly if Gemstone is doing VM modifications to make this work, it
would be nice to have an implementation done properly the first time so we
have some flexibility.

Julian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20090204/35526eac/attachment-0001.htm