A mechanism to start over the topology when the topology crashes.
If a Quarks thread abruptly terminates due to an uncaught exception the runtime shuts down. There are several alternatives for preventing the Quarks application from becoming unavailable:
Restart the failed oplet. In the ETIAO runtime, a source and all downstream oplet invocations (up to an Isolate) will execute in the same thread, so the runtime needs to restart the failed path.
Have a monitor service which resubmits the topology in case it is shut down.
A mechanism to start over the topology when the topology crashes.
If a Quarks thread abruptly terminates due to an uncaught exception the runtime shuts down. There are several alternatives for preventing the Quarks application from becoming unavailable:
Any thoughts or comments?