In the event the kernel tries to take control from the program (i.e. the user presses (Ctrl/Cmd) + C simultaneously, causing a interrupt), we need to either:
force back control from the kernel and resume execution.
offload all the current progress made to a database, and load it up when re-executed.
I will set up a Pull Request soon to incorporate both changes, then accesses a .so linked runtime library which provides a setting on whether or not to execute Strategy 1 or Strategy 2 (the runtime library helps for a "hot reload" when the value is changed in the library).
In the event the kernel tries to take control from the program (i.e. the user presses (Ctrl/Cmd) + C simultaneously, causing a interrupt), we need to either:
I will set up a Pull Request soon to incorporate both changes, then accesses a
.so
linked runtime library which provides a setting on whether or not to execute Strategy 1 or Strategy 2 (the runtime library helps for a "hot reload" when the value is changed in the library).