NeuroKernel has very familiar task execution schema compared to main stream operating systems. Kernel can directly execute tasks, or applications can request new task execution. Applications can also spawn plugin tasks and plugin task branches. Applications can be either registered or unregistered. It is possible to deploy single applications for remote use by others.
Registered applications run in privileged mode with all resource accesses are granted by kernel when available. Unregistered applications are collectively called remote applications, they can be a deployed to any medium including torrent networks and IPFS. Remote applications have limited access to the resources and their protocol is scanned before executed. Applications can be compiled in JS, Bytecode or WASM(Experimental). A task can run in a worker as well while still be able to render its interface and graphics.
1. Using Terminal
The terminal console application that comes default in all deployment packages is capable of executing any application registered or not from its command line. The
rexec terminal commands are used to execute a new application. Registered applications can be executed directly by giving their registered name as command. Command to run a new terminal console is
2. Using API
IRuntime system interface is used to spawn a new task from inside another task programmatically. The unregistered remote applications can not use the bulk of this interface because of the sandbox applied to them. The application will be notified about the failure or success of the execution process of the new application.
3. Using System Manager
System manager application is also included default by all editions to manage tasks, windows and user preferences such as logout or password change. Its user interface has controls to execute new tasks. It shows all tasks currently running in a table view. The command to run system manager is
4. Using Desktop Manager