Continuations in Seaside

[Sohail Somani]

I'm following the Seaside newsgroup/mailing list and there seems to be a
drive to move away from continuations. Any ideas why and what this means
for Weblocks? I know Slava points to Seaside as an example of a good
framework.

--
Sohail Somani
http://uint32t.blogspot.com

[Vyacheslav Akhmechet]

Well, Seaside uses a slightly different model. They use persistent
continuations in order to maintain UI state indefinitely. They also
store much of UI state in continuations to deal with back button
issues. I suppose this makes continuations pretty expensive in
seaside. Weblocks takes a different approach - continuations are used
purely to write code comfortably. They're not persisted and they're
delimited (which means they're simple closures). This makes them
pretty lightweight and nice to use. So, to answer your question, their
decision means very little for the future of Weblocks :)

I'd be interested in learning their rationale in more detail. I'll
watch their list (or shoot an email to one of the devs).

Regards,
Slava Akhmechet

[Sohail Somani]

Ah, thanks for the lesson. To be clear, I think one of the developers/
users was advocating making them optional, but I could not see why in the
thread.

[Vyacheslav Akhmechet]

Do you have a link? I can't find it on google.

[Sohail Somani]

http://www.nabble.com/Continuations---their-future--
tt14246898.html#a14246898

On Thu, 13 Dec 2007 13:39:22 -0500, Vyacheslav Akhmechet wrote:

> Do you have a link? I can't find it on google.

--
Sohail Somani
http://uint32t.blogspot.com