Luke Hubbard wrote:
Sure it is possible with threads, but it will mean one thread per process running or waiting. For my application that could mean lots of threads. What I wanted to do was capture a continuation, then store it in the db, and restore it later ( thats possible in rhino and java ). This allows process execution to continue even if the app was restarted and for multiple servers to handle the workload. All good fun really.
It may be a little different from the mainstream but AFAIK Termite [1] offers all you need. It's a module for the Gambit Scheme [2] compiler which brings Erlang-style concurrency to Scheme. I'm not sure but maybe even pure Gambit Scheme would offer the continuation serialization you require.
[1] http://toute.ca/termite.pdf [2] http://www.iro.umontreal.ca/~gambit/ -- regards, Jakub Piotr Cłapa -- Neko : One VM to run them all (http://nekovm.org)
