Kstore event manager using triggers for K
The KStore or K is a datastore made up of a forest of interconnected, highly unconventional trees of one or more levels. A KStore event manager monitors events and polls for KStore state. When triggered by user-defined conditions or receiving notification that a specified event has occurred, a specified response can be executed. An event/condition/response is defined through a KStore event wizard. When a triggering condition is detected or a notification of an event is received, a user-defined action or sequence of actions is performed automatically, without further user interaction.
1 . A system for managing events in a KStore comprising:
an event manager comprising:
a wizard or background feature that receives or obtains
user input specifying a KStore state, a polling interval and a first action to be performed in response to detecting the specified KStore state or
user input specifying an internal KStore event and a second action to be performed in response to receiving a notification that the internal KStore event has occurred; and
an event processor that executes
the first action in response to detecting the specified KStore state or
the second action in response to receiving the notification that the internal KStore event has occurred, wherein the KStore comprises an interlocking trees datastore comprising elemental root nodes, subcomponent nodes and end product nodes linked by asCase and asResult bi-directional links that create asCase and asResult paths within the interlocking trees datastore, wherein an asCase path comprises a sequence of subcomponent nodes linked with bi-directional asCase links ending with an end product node and where each subcomponent node in the asCase path has a bi-directional asResult link to an elemental root node or end product node comprising an asResult tree.
2 . The system of claim 1 , wherein the KStore Event Manager directs a KStore API utility to direct a K Engine to send the notification to the KStore Event Manager when the specified internal KStore event occurs.
3 . The system of claim 1 , wherein the KStore Event Manager directs a KStore API utility to run a polling application to detect attainment of the specified KStore state.
4 . The system of claim 1 , further comprising:
an event store that stores the user-specified KStore state, the polling interval and the first action.
5 . The system of claim 1 , further comprising:
an event definition store that stores the user-specified internal KStore event and the second action.
6 . The system of claim 1 , wherein a response comprises an action, event, sequence of actions or sequence of events.
7 . The system of claim 3 , further comprising:
the polling application that polls the KStore based on the specified polling interval.
8 . A method for managing events in a KStore comprising:
receiving user input, the user input comprising a response comprising an action, event, sequence of actions or sequence of events;
in response to determining that the user input further comprises a user-specified state to be monitored for in the KStore, prompting and receiving a polling interval at which the KStore is polled for the user-specified state and executing the response in response to detecting the user-specified state in the KStore; or
in response to determining that the user input further comprises a user-specified event, directing a K Engine to send a notification to an event manager, prompting for and receiving the user input comprising the response and executing the response in response to receiving the notification, wherein the KStore comprises an interlocking trees datastore comprising elemental root nodes, subcomponent nodes and end product nodes linked by asCase and asResult bi-directional links that create asCase and asResult paths within the interlocking trees datastore, wherein an asCase path comprises a sequence of subcomponent nodes linked with bi-directional asCase links ending with an end product node and where each subcomponent node in the asCase path has a bi-directional asResult link to an elemental root node or end product node comprising an asResult tree.
9 . The method of claim 8 , wherein the response comprises an action, event, sequence of actions or sequence of events.
10 . The method of claim 8 , wherein a polling application monitors the KStore for the specified state by periodically polling the KStore.
11 . The method of claim 8 , wherein the wizard collects the user input through a GUI interface.
12 . The method of claim 8 , wherein the user input is collected via a background job that collects the user input from an application or from an existing well-defined set of user input.
13 . The method of claim 8 , further comprising:
monitoring for the specified KStore state or for the specified KStore event via the KStore API.
14 . A computer-readable medium comprising computer-executable instructions that when executed cause a computing environment to:
receive user input, the user input comprising a response comprising an action, event, sequence of actions or sequence of events;
in response to determining that the user input further comprises a user-specified state to be monitored for in the KStore, prompt for a polling interval at which the KStore is polled for the user-specified state, wherein the KStore comprises an interlocking trees datastore comprising elemental root nodes, subcomponent nodes and end product nodes linked by asCase and asResult bi-directional links that create asCase and asResult paths within the interlocking trees datastore, wherein an asCase path comprises a sequence of subcomponent nodes linked with bi-directional asCase links ending with an end product node and where each subcomponent node in the asCase path has a bi-directional asResult link to an elemental root node or end product node comprising an asResult tree.
15 . The computer-readable medium of claim 14 , comprising further computer-executable instructions that when executed cause the computing environment to:
receive the polling interval and direct a KStore API utility to run a polling application to poll the KStore.
16 . The computer-readable medium of claim 15 , comprising further computer-executable instructions that when executed cause the computing environment to:
execute the response in response to detecting the user-specified state in the KStore.
17 . The computer-readable medium of claim 14 , comprising further computer-executable instructions that when executed cause the computing environment to:
in response to determining that the user input further comprises a user-specified event, direct a K Engine to send a notification to an event manager.
18 . The computer-readable medium of claim 17 , comprising further computer-executable instructions that when executed cause the computing environment to:
prompt for and receive the user input comprising the response.
19 . The computer-readable medium of claim 18 , comprising further computer-executable instructions that when executed cause the computing environment to:
execute the response in response to receiving the notification.
20 . The computer-readable medium of claim 14 , comprising further computer-executable instructions that when executed cause the computing environment to:
receive the user input via a GUI interface or via a background job that collects existing user input.