Mechanisms to support fine-grain namespacing

• US 8,229,974 B2
• Filed: 08/05/2008
• Issued: 07/24/2012
• Est. Priority Date: 08/05/2008
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Lowry, Lee Edward, Scheuber-Heinz, Volker Gunnar, Street, William, Thurgood, Brent, Cox, Ryan, Carter, Stephen R, Vasudevan, Rajesh
• Primary Examiner(s): Cottingham, John
• Assistant Examiner(s): Arjomandi, Noosha
• Application Number:
  US12/186,143
• Publication Number:
  US 20100036869A1
• Time in Patent Office: 1,449 Days
• Field of Search: 707/803, 707/999.103, 717/120, 719/313
• US Class Current: 707/803
• CPC Class Codes: G06F 8/20 Software design

Abstract

Mechanisms to support fine-grain namespacing are provided. When an object is to be loaded within a processing environment, a specific namespace for that object is dynamically resolved during the load. That namespace can be dynamically resolved via object inheritance, via specific object-attribute declaration, and/or via consultation with a namespace object.

Claims

1. A method for object namespace resolution residing in a non-transitory computer-readable storage medium and for execution on a machine, comprising:

receiving a request to load an object, the object is a particular resource that processes as executable instructions on the machine;

resolving a namespace for the object that is specific to the object in response to the request, the namespace is separate from other namespaces associated with other objects of a project and the object also having multiple different and disparate namespaces from the namespace and the multiple different and disparate namespaces exists together within a same project processing environment for the project with the namespace; and

loading the object to that namespace to satisfy the request, wherein said loading includes simultaneously loading the object or selective portions of the object to a second and entirely different namespace from the namespace in response to a namespace attribute of the object that declares the namespace and the second namespace.

2. The method of claim 1, wherein receiving further includes iterating a project model schema to load the object and multiple other objects associated with the project for processing.

3. The method of claim 1, wherein resolving further includes identifying the namespace as being inherited from a previous object, wherein the previous object declared the namespace as an attribute of that previous object.

4. The method of claim 1, wherein resolving further includes identifying the namespace as a value associated with a namespace attribute declared in the object.

5. The method of claim 1, wherein resolving further includes resolving the namespace by using a name assigned to the object to question a namespace object that responds with the namespace in response to that name.

6. The method of claim 5, wherein resolving further includes recognizing the name as an object hierarchy to which the object belongs.

7. The method of claim 1 further comprising one or more of the following:

assigning access rights to the object in response to policy evaluation that utilizes the namespace;

selectively encrypting portions of the object in response to the namespace; and

porting selective portions of the object to an entirely different namespace from the namespace.

8. A machine implemented method residing in a non-transitory computer-readable storage medium and for execution on a machine, comprising:

parsing an object schema to load an object into a project processing environment, the object is a particular resource that processes as executable instructions on the machine;

determining an object name from the object schema;

using the object name to resolve a namespace for the object unless the namespace is declared within the object schema, the namespace is specific to the object and separate from other namespaces used by other objects of a project within the project processing environment, and the object having multiple different and disparate namespaces; and

loading the object to the namespace within the project processing environment, wherein said loading includes simultaneously loading the object or selective portions of the object to a second and entirely different namespace from the namespace in response to a namespace attribute of the object that declares the namespace and the second namespace.

9. The method of claim 8, wherein using further includes consulting a namespace object with the object name to resolve the namespace.

10. The method of claim 8, wherein using further includes referencing an object hierarchy using the object name to obtain the namespace as an inherited namespace from another object of the object hierarchy.

11. The method of claim 8, wherein using further includes recognizing that the namespace is declared in the object schema and maintaining that namespace as an override to a previous namespace that was to be associated with the object name.

12. The method of claim 8, wherein loading further includes setting access rights and security roles on the object in response to the namespace and in view of policy evaluation.

13. The method of claim 8, wherein loading further includes selectively configuring policies and operational settings for the object in response to the namespace.

14. A machine-implemented system, comprising:

a machine having an object implemented in a non-transitory machine-accessible and readable medium and to process on the machine; and

the machine also having an object loader implemented in a non-transitory machine-accessible and readable medium and to process on the machine;

wherein the object loader selectively loads the object to a particular namespace, the namespace is independent of other namespaces for other objects and different from the other namespaces and the namespace is specific to the object, the object having multiple different and disparate namespaces, wherein the object loader further loads the object or selective portions of the object to a second and entirely different namespace from the namespace in response to a namespace attribute of the object that declares the namespace and the second namespace, and wherein the object and the other objects belong to a same object hierarchy, the object is a particular resource that processes as executable instructions on the machine.

15. The system of claim 14, wherein the object loader resolves the namespace via inheritance from the object hierarchy.

16. The system of claim 14, wherein the object loader resolves the namespace via an assigned namespace attribute value declared in the object.

17. The system of claim 14, wherein the object loader resolves the namespace by consulting a namespace object with a name for the object to acquire the namespace.

18. The system of claim 14, wherein the object loader sets resource roles, access rights, and configuration settings for the object within the namespace based on the namespace associated with the object.

19. A machine-implemented system, comprising:

a machine having a project model schema implemented in a non-transitory machine-accessible and readable medium and that defines objects which process on the machine; and

the machine also having a loader implemented in a non-transitory machine-accessible and readable medium and to process on the machine;

wherein the loader parses the project model schema to selectively load an object into a first namespace and selective load portions of the object to a second and entirely different namespace from the first namespace in response to a namespace attribute of the object that declares the first namespace and the second namespace, the loaded object or portions thereof in their respective namespaces cooperate as a project defined by the project model schema, and each namespace is resolved by the loader from the project model schema, each namespace being particular to a particular object and the particular object having multiple different and disparate namespaces, and wherein the namespaces exists together within a same project processing environment for the project, the object being a particular resource that processes as executable instructions on the machine.

20. The system of claim 19, wherein some of the namespaces are explicitly defined within the project model schema via attribute declarations assigned to some of the objects.

21. The system of claim 19, wherein some of the namespaces are implicitly resolved via relationships between some of the objects that are present within the project model schema.

22. The system of claim 19, wherein the namespaces are resolved by consulting a namespace object with names from the objects as defined within the project model schema.

23. The system of claim 19, each namespace includes its own unique access rights and configuration settings defined by policy.