![]()
JaHOVA is built around Cores...
Each core is designed with an Application API and a JaHOVA API. The Application APIs are the methods available to any application. The JaHOVA APIs are the interface methods for the JaHOVA OS Kernel to the Core. The APIs can be user defined as long as the interface definition conforms to the OS rules. This allows for users to extend or create their own cores and add them to JaHOVA. Standard core deployment does not allow for any direct connection between cores and/or applications. Each core must register with the Kernel Resource and Schedule Manager Module. Once registered the core can then be activated, which allows the core to receive instructions from applications and OS via the Kernels Instruction Module. The APIs generate messages which are sent to the JaHOVAs Kernel. The Kernel then routes to the proper location for delivery via the Kernels Instruction Module. This allows JaHOVA to accept messages from remote systems and /or send messages to remote systems. This is essential to allow for cloud computer clustering. The Kernel can use this capability to offload message request to available clients and thereby perform parallel computing in the cloud. This technique also allows for sharing of Cores. For instance, an application on a local machine could have an Application API but not the JaHOVA API or JavaScript Core. When messages are received by the Application API for a nonexistent core, the message can be routed to a remote machine which can process the message and pass back the response. This technique also allows for load balancing. If an remote machine is idle and has the proper core available, the local machine may decided to ship the message off for processing if high priority message are waiting for delivery/processing in the local OS.
Comments