Mechanisms to support fine-grain namespacing
First Claim
Patent Images
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.
11 Assignments
0 Petitions
Accused Products
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.
-
Citations
23 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. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
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. - View Dependent Claims (9, 10, 11, 12, 13)
-
-
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. - View Dependent Claims (15, 16, 17, 18)
-
-
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. - View Dependent Claims (20, 21, 22, 23)
-
Specification