Isn't that still brain-damaged? You are alleviating the problem rather than fixing the cause. The cause being using closures means you have to store data for all clients for an unknown amount of time instead of having each client store their own data; it does not scale.
We did that sort of thing in our CPS Web-app. You can give semi-permanent URI to the continuation closure, if the closure only refers to the persistent objects and not any transient state; for example, the "reply" link attached to each comment.
The link works as far as the persistent object (in the "reply" link case, the comment) lives.
Comments
OK, will look into it. The right thing is probably to gc closures waiting for form submissions much more slowly.
Isn't that still brain-damaged? You are alleviating the problem rather than fixing the cause. The cause being using closures means you have to store data for all clients for an unknown amount of time instead of having each client store their own data; it does not scale.
http://news.ycombinator.com/item?id=24790
Do you create one closure/session/page? Why not just one semi-permanent closure/page?
We did that sort of thing in our CPS Web-app. You can give semi-permanent URI to the continuation closure, if the closure only refers to the persistent objects and not any transient state; for example, the "reply" link attached to each comment. The link works as far as the persistent object (in the "reply" link case, the comment) lives.