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.
- Luke On 4/18/07, skaller < [EMAIL PROTECTED]> wrote:
On Wed, 2007-04-18 at 17:40 +0700, Luke Hubbard wrote: > Thanks for quick reply.. it seems its not possible with continuations > and haXe server then. > > One other possibility is to use Neko Threads for > synchronization between > tasks. One thread waits for messages and worker threads sleep > until the > task is resolved before notifying the main thread. Look at the > neko.vm.Thread haXe API. I'm curious why Neko threads won't suffice. [Heh .. Felix has the continuations you need .. but can't serialise data automatically] -- John Skaller <skaller at users dot sf dot net> Felix, successor to C++: http://felix.sf.net
-- Luke Hubbard codegent | coding for the people http://www.codegent.com NMA Top 100 Interactive Agencies - Ones to watch! http://www.codegent.com/top100/ want to know more? http://www.codegent.com/showreel/ This e-mail may contain information which is privileged, confidential and protected from disclosure. If you are not the intended recipient of this e-mail, or any part of it, please delete this email and any attachments immediately on receipt. You should not disclose the contents to any other person or take copies. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of codegent limited.
-- Neko : One VM to run them all (http://nekovm.org)
