[Seaside-dev] Seaside-Flow

[Lukas Renggli]

>> (1) It is a decoupling, not a coupling.
>
> It's coupling in that Flow can now only be used with the existing
> ActionCallback as opposed to anywhere that leaves an appropriate
> marker.

Give me a real-world scenario where a marker would be needed somewhere else.

And even if a different location is needed, another location can
easily be specified by changing the method WAComponent>>#wait:.

> It's also coupling in that you cannot (as far as I can see)
> provide an alternate implementation using two full continuations
> without hacking core.

I don't think that the two full continuation trick is practically
useful. Unless combined with a nearby process monitor it's a huge
memory leak.

> The latter is not the end of the world in that ports can hack core if
> needed. The first is somewhat theoretical but since I would like
> people like Colin to be able to implement alternative frameworks using
> our base pieces I still kind of think it sucks.

There is no point in trying to solve all possible problems. We should
strive for simplicity, not for absolute generality. I don't see a
reason why Colin wouldn't be able to implement something alternative
using most of the present base pieces.

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch