Dynamic data structures

• US 8,819,077 B1
• Filed: 06/30/2011
• Issued: 08/26/2014
• Est. Priority Date: 06/30/2011
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: van Rotterdam, Jeroen, Polman, Mark
• Primary Examiner(s): VO, TRUONG V
• Application Number:
  US13/174,740
• Time in Patent Office: 1,153 Days
• Field of Search: 707/610, 707/792, 707/793, 707/802, 707/807, 707/674, 707/803
• US Class Current: 707/802
• CPC Class Codes: G06F 16/81 Indexing, e.g. XML tags; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/83 Querying

Abstract

A method, article of manufacture, and apparatus for managing a cloud computing environment. In some embodiments, this includes instantiating an object, modifying a trait of the object at runtime, storing the modified object in a storage device. In some embodiments, the object may include required traits. In some embodiments, modifying a trait includes adding a trait.

Claims

1. A method for organizing data, the method comprising:

instantiating an object, wherein the object includes a required trait and a user added trait, wherein the required trait is associated with a known schema, and wherein the object includes object restrictions, wherein the object restrictions define which traits can be added to the object, wherein the object restrictions are based on performance issues, and wherein event handlers of the required trait are determined by an event configuration;

validating the required trait by comparing the required trait to the known schema, wherein the required trait includes an XML document and wherein the XML document includes a namespace, and wherein a schema location is identified in the XML document;

validating the user added trait based on at least the object restrictions;

upon validation of the required trait, adding the required trait to the object at runtime;

upon validation of the user added trait, adding the user added trait to the object at runtime; and

storing the modified object in a storage device.

2. The method of claim 1, wherein the object restrictions limits an amount of traits added to the object at runtime.

3. The method of claim 2, wherein the amount of traits is based on a performance threshold.

4. The method of claim 1, wherein the object restrictions limits a trait in a set of traits to being added to a set of objects.

5. The method of claim 1, wherein the object restrictions restricts a trait in a set of traits from being added to a set of objects.

6. A system for organizing data, comprising a storage device and a processor configured to:

instantiate an object, wherein the object includes a required trait and a user added trait, wherein the required trait is associated with a known schema, and wherein the object includes object restrictions, wherein the object restrictions define which traits can be added to the object, wherein the object restrictions are based on performance issues, and wherein event handlers of the required trait are determined by an event configuration;

validate the required trait by comparing the required trait to the known schema, wherein the required trait includes an XML document and wherein the XML document includes a namespace, and wherein a schema location is identified in the XML document;

validate the user added trait based on at least the object restrictions;

upon validation of the required trait, add the required trait to the object at runtime;

upon validation of the user added trait, add the user added trait to the object at runtime; and

store the modified object in a storage device.

7. A computer program product for organizing data, comprising a non-transitory computer readable medium having program instructions embodied therein for:

instantiating an object, wherein the object includes a required trait and a user added trait, wherein the required trait is associated with a known schema, and wherein the object includes object restrictions, wherein the object restrictions define which traits can be added to the object, wherein the object restrictions are based on performance issues, and wherein event handlers of the required trait are determined by an event configuration;

validating the required trait by comparing the required trait to the known schema, wherein the required trait includes an XML document and wherein the XML document includes a namespace, and wherein a schema location is identified in the XML document;

validating the user added trait based on at least the object restrictions;

upon validation of the required trait, adding the required trait to the object at runtime;

upon validation of the user added trait, adding the user added trait to the object at runtime; and

storing the modified object in a storage device.