@restioson Nothing prevents you from writing project/library with serializable coroutines -- all the core implementation classes (state machine impls) are designed to be serializable (they even implement java.io.Serializable marker for what it worth). As long as locals of each coroutine are serializable, you are good to go. Btw, what do you what to achieve?
Thread in Slack Conversation
@elizarov, maybe
@restioson is thinking of implementing something like the Seaside Smalltalk webserver (
http://seaside.st/). IIRC it has the async "call" being the sending of a web page to the client, and the "return" being the next request in a session-tied flow, which can be implemented as a single method (or nested method calls). I imagine you would serialise each continuation between response/request pairs if you didn't want them to use up memory and/or wanted them to survive a server restart.