I know that my question is more academic than a real issue. In most cases a thread implementation with Fiber-like logic would be OK. But is there any way to implement Fibers as they are described in the JVM?
Is there any framework that is missing me to achieve that?
There were/are Java EE frameworks, that enable to have a class with normal control flow like a Java SE application, and thus maintain state. To function over HTTP at specific points the classes instance is serialized, a response is made to the client, and on the next request the instance is deserialized and continues. This is not a general purpose coroutine solution, and I would certainly not call fibers.
Unfortunately its name slips my mind. But that was a specific case of running one single coroutine transfering control to the framework coroutine.
AOP offers another mean to switch control. Could maybe be used to implement fibers.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With