special K...

I’m a great fan of continuations and frameworks like Seaside. Sadly they will be dropped from Ruby in the future. (Or Not?) Ian Griffiths has some nice arguments against using continuation for webframeworks. I share some of his doubts, but I would not be suprised if some smart guy can solve most of the problems. For example the mentioned “back” problem is a “where do you store the continuation” problem I think. You have at least some options not to store everything on the server like hidden fields, cookies, URLs or a combination of server and client side storage. A nifty idea to make this more handable may be composable continuation.