US 2019/0377769 A1 · FUNCTION AND MEMORY MAPPING REGISTRY WITH REACTIVE MANAGEMENT EVENTS

Abstract

A system for managing data content and data content relationships through resource efficient process structures for cloud and network environments includes a Clode core. The Clode core creates an object/display/process based on a defined order of processes determined by the object's tags and/or relationships to a function map and/or other objects in the system. This is used in Clode tag modules such as ‘clode:autopublish’ to create a data publication on the server, by ‘clode:autosubscribe’ to make client's automatically subscribe to data related to the tagged object, and by ‘clode:surface’ to manage an object on a display; just to name a few use cases. Tags can then be used to manage third party environments such as a docker container that would be classified as having the tag ‘on’, but when removed could cause the container to shut off. Tag management functions could also change the classifications as to say in the previous example to cause a tag to be added called ‘off’.

Claims18

Dependent claims

A system for managing data content and data content relationships through resource efficient process structures for cloud and network environments, comprising:

a Clode object including a JSON object having at least one data file with a list of tags;
a Clode core, the Clode core being a primary function in the native language that takes the Clode object;
an in-memory storage, the in-memory storage stores functions and large objects;
a tag inspection component, the tag inspection component inspects the list of tags of the at least one data file in the Clode core and determines whether each tag in the list of tags matches as a function in the in-memory storage;
and
a call function component, the call function component calls the function, assigns an entire object including fields, tags and identifiers to be interpreted and/or modified to each tag in the list of tags determined to be a function and passes the object in the Clode object.

3 more elements

A system for managing data content and data content relationships through resource efficient process structures for cloud and network environments, comprising:

a Clode object including a JSON object having at least one data file with a list of tags;
a Clode core, the Clode core being a primary function in the native language that takes the Clode object;
an in-memory storage, the in-memory storage stores functions and large objects;
a tag inspection component, the tag inspection component inspects the list of tags of the at least one data file in the Clode core and determines whether each tag in the list of tags matches as a function in the in-memory storage;
a call function component, the call function component calls the function, assigns an entire object including fields, tags and identifiers to be interpreted and/or modified to each tag in the list of tags determined to be a function and passes the object in the Clode object;
a tag check component, the tag check component checks a tag field of the Clode object to determine whether there is a remaining tag that hasn't been processed;
a tag passing component, the tag passing component takes a current tag in process from the tag check component and passes the current tag in process to the tag inspection component;
a Clode:function, the Clode:function takes the Clode object having a tag “clode:function” in the tag field;
an environmental check component, the environmental check component checks the tag field of the Clode object for a tag having “clode:server” and/or “clode:client” and checks the current environment to determine if the command is running in the right location (client, server, or both);
an in-memory database with query layer or registry and a tag query component, the tag query component queries the registry to determine whether the tag field in the Clode object was previously used to register a tag of the same name;
a tag storage component, the tag storage component stores a function value of a field “clode:function” from the Clode object into the in-memory storage using the tag field as a key;
a remove function component, the remove function component deletes a “clode:function” field from the Clode object and stores remaining data in the registry;
a clode:observe component, the clode:observe component reacts to behaviors of the Clode object having a tag “clode:observe” in the registry;
a changed object component, the changed object component reacts when the Clode object's fields have changed in the registry;
a removal tag component, the removal tag component comprising a data observation method to determine which tags in the tag field of the Clode object have been removed;
a changed add tag component, the changed add tag component adds tags to the tag field of the Clode object, a copy of each existing tag with the added text “:changed” at the end to later be processed by the Clode core;
a removed add tag component, the removed add tag component adds tags to the tag field of the Clode object, a copy of each existing tag with the added text “:removed” at the end to later be processed by the Clode core;
a get added tag component, the get added tag component including a data observation method of the Clode object that determines which tag in a tag field have been added;
a tag values determining component, the tag values determining component determines if there is any remaining values of the Clode object tag field that has not yet been processed;
a tag add component, the tag add component adds tags to the tag field of the Clode object, a copy of each existing tag with the added text “:added” at the end to be later processed by the Clode core;
and
an object pass component, the object pass component takes and passes the Clode object to the Clode core.

19 more elements

A system for managing data content and data content relationships through resource efficient process structures for cloud and network environments, comprising:

a Clode object including a JSON object having at least one data file with a list of tags;
a Clode core, the Clode core being a primary function in the native language that takes the Clode object;
an in-memory storage, the in-memory storage stores functions and large objects;
a tag inspection component, the tag inspection component inspects the list of tags of the at least one data file in the Clode core and determines whether each tag in the list of tags matches as a function in the in-memory storage;
a call function component, the call function component calls the function, assigns an entire object including fields, tags and identifiers to be interpreted and/or modified to each tag in the list of tags determined to be a function and passes the object in the Clode object;
a tag check component, the tag check component checks a tag field of the Clode object to determine whether there is a remaining tag that hasn't been processed;
a tag passing component, the tag passing component takes a current tag in process from the tag check component and passes the current tag in process to the tag inspection component;
a Clode:function, the Clode:function takes the Clode object having a tag “clode:function:
in the tag field;
an environmental check component, the environmental check component checks the tag field of the Clode object for a tag having “clode:server” and/or “clode:client” and checks the current environment to determine if the command is running in the right location (client, server, or both);
an in-memory database with query layer or registry and a tag query component, the tag query component queries the registry to determine whether the tag field in the Clode object was previously used to register a tag of the same name;
a tag storage component, the tag storage component stores a function value of a field “clode:function” from the Clode object into the in-memory storage using the tag field as a key;
a remove function component, the remove function component deletes a “clode:function” field from the Clode object and stores remaining data in the registry;
a clode:observe component, the clode:observe component reacts to behaviors of the Clode object having a tag “clode:observe” in the registry;
a changed object component, the changed object component reacts when the Clode object's fields have changed in the registry;
a removal tag component, the removal tag component comprising a data observation method to determine which tags in the tag field of the Clode object have been removed;
a changed add tag component, the changed add tag component adds tags to the tag field of the Clode object, a copy of each existing tag with the added text “:changed” at the end to later be processed by the Clode core;
a removed add tag component, the removed add tag component adds tags to the tag field of the Clode object, a copy of each existing tag with the added text “:removed” at the end to later be processed by the Clode core;
a get added tag component, the get added tag component including a data observation method of the Clode object that determines which tag in a tag field have been added;
a tag values determining component, the tag values determining component determines if there is any remaining values of a Clode object tag field that has not yet been processed;
a tag add component, the tag add component adds tags to the tag field of the Clode object, a copy of each existing tag with the added text “:added” at the end to be later processed by the Clode core;
an added object component, the added object component reacts to the Clode object having been added to the registry;
a tag as blank object component, the tag as blank object component creates a memory address in the in-memory storage with a key equal to the tag field of the Clode object;
a field remove component, the field remove component deletes a field inside of a memory address created by the tag as blank object component;
a next unused tag component, the next unused tag component uses a next or first unused tag in the Clode object tag field as a current tag in process;
a field add component, the field add component adds a field in memory created by the tag as blank object component inside the in-memory storage equal to the tag in process from the next unused tag component;
a removed Clode object component, the removed Clode object component comprising a function that is spawned when the Clode object is removed from the registry;
a memory address remove component, the memory address remove component deletes all memory at a location created in the in-memory storage equal to the key used in the tag as blank object component;
and
an object pass component (129), the object pass component takes and passes the Clode object to the Clode core.

27 more elements

Dependencies are inferred from the claim text.

Function and memory mapping registry with reactive management events

Life of this patent

Function and memory mapping registry with reactive management events

Life of this patent

Abstract

Claims18