Loading patent…
AssigneeMicrosoft Corporation
InventorsClemens A. Szyperski, Brad M. Olenick, Balasubramanian Shyamsundar, Arshad F. Ahmad, Arthur H. Watson
Estimating the term…
Strategies are described for organizing the runtime components of an application into an entity domain framework. The entity domain framework includes one or more entity domains arranged in a hierarchical fashion. Each entity domain further groups one or more components together in a hierarchical fashion. Each entity domain can include one or more services that provide a policy to the components within the entity domain. Composite functionality couples the framework together, and further provides a bus-like mechanism whereby an entity can forward service requests up through the hierarchy until a domain is found that satisfies the requests. Exemplary services provided by the entity domain framework include lifetime management services, error handling services, and so forth. The hierarchical structure provides an efficient way of exposing functionality to groups of components that will share this functionality in a common context, without requiring costly and complex atomistic coupling of services to components or duplication of service instances.
A method for running machine-readable code that includes a collection of components at runtime, the method comprising;
A machine-readable storage medium providing a data structure that implements an entity domain framework, the data structure comprising:
An apparatus for providing an application, the apparatus comprising:
A method for running machine-readable code that includes a collection of components at runtime, the method comprising:
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
From the US filing history. Foreign family members aren’t listed.
About 2 years 3 months of term left · ends 14 Jan 2029 (estimated)
This subject matter relates to improved strategies for managing machine-readable code components.
Applications can perform their prescribed tasks using a collection of code components. In the illustrative case of object-oriented programming, for example, applications can allocate, in their source code, different classes that can be used at runtime to provide functionality for performing defined tasks. Namely, at runtime, a computing machine can instantiate these classes to provide specific objects (also referred to as “instances”). These objects are stored in an allocated portion of the computing machine's memory. After these objects have served their respective purposes and are no longer needed, the computing machine can run so-called garbage collection functionality to remove these objects from memory, thus providing room for the creation and storage of additional objects.
At any given time in the application's runtime performance, the computing machine's memory can be expected to store a large collection of runtime code components. These code components must interact with each other to perform their prescribed tasks. To this end, an application will provide functionality for “wiring” these code components together. The wiring allows components to refer to other components, such that the components can exchange information among themselves to perform their allotted tasks.
FIG. 1 illustrates an exemplary organization of components into an entity domain framework.
FIG. 2 illustrates an exemplary collection of services available within the entity domain framework of FIG. 1.
FIG. 3 illustrates the operation of exemplary lookup functionality that can be used to look up services in the entity domain framework of FIG. 1.
The same numbers are used throughout the disclosure and figures to reference like components and features. Series 100 numbers refer to features originally found in FIG. 1, series 200 numbers refer to features originally found in FIG. 2, series 300 numbers refer to features originally found in FIG. 3, and so on.
The following description sets forth exemplary strategies for grouping components into an entity domain framework and for managing the components using this framework. The entity domain framework can organize the components into a hierarchical structure of entity domains. Each entity domain can include one or more element components and composite functionality. The composite functionality groups the element components together within an entity domain. The entity domain framework also couples the composite functionality of respective entity domains together to create the hierarchical structure of entity domains.
Each entity domain can provide one or more services. Generally, entities are precluded from directly interacting with the entity domain framework. An entity within the entity domain framework can access a service using lookup functionality. The lookup functionality accesses the service by moving up through the hierarchy, successively determining whether each entity domain can furnish the requested service.