Abstract: A method can include storing information about the business service in one or more template type layers; storing information about an instance of the business service in one or more instance type layers; wherein the template type layers include one or more checkpoints that reference information stored in a content addressable store that defines an expected structure of the business service, wherein at least one checkpoint of the template type layers includes a timestamp and a hash value associated with an entry in the content addressable store; and wherein the instance type layers include one or more checkpoints that reference information stored in the content addressable store that defines attributes of the instance of the business service, wherein at least one checkpoint of the instance type layers includes a timestamp and a hash value associated with an entry in the content addressable store.

Abstract: A method may include receiving a first record associated with a first configuration item from a first data source and a second record associated with a second configuration item from a second data source; identifying a relationship between the first configuration item and the second configuration item based on the first record and the second record; identifying a relationship rule governing the relationship between the first configuration item and the second configuration item; determining that the relationship between the first configuration item and the second configuration item is inconsistent with the relationship rule; remediating the relationship between the first configuration item and the second configuration item such that the relationship is consistent with the relationship rule; and allowing the first record and the second record to be stored in the configuration management database in response to remediating the relationship.

Abstract: Systems and methods for the identification and reconciliation of network resource information are herein disclosed. In an implementation, a system includes instructions stored in memory for processing a request received from a data source to update a record of a network resource by receiving data relating to an attribute of a network resource of a computer network from a first data source, wherein the network resource is associated with a configuration item of a configuration management database, the configuration item including data relating to the attribute from a second source; determining that the first data source is authoritative for the attribute based on a priority of the first data source, a priority of the second data source, and a staleness period of the second data source; and processing the request by updating the attribute based on the data.

Abstract: A method can include storing information about the business service in one or more template type layers; storing information about an instance of the business service in one or more instance type layers; wherein the template type layers include one or more checkpoints that reference information stored in a content addressable store that defines an expected structure of the business service, wherein at least one checkpoint of the template type layers includes a timestamp and a hash value associated with an entry in the content addressable store; and wherein the instance type layers include one or more checkpoints that reference information stored in the content addressable store that defines attributes of the instance of the business service, wherein at least one checkpoint of the instance type layers includes a timestamp and a hash value associated with an entry in the content addressable store.

Abstract: A method can include storing information about the business service in one or more template type layers; storing information about an instance of the business service in one or more instance type layers; wherein the template type layers include one or more checkpoints that reference information stored in a content addressable store that defines an expected structure of the business service, wherein at least one checkpoint of the template type layers includes a timestamp and a hash value associated with an entry in the content addressable store; and wherein the instance type layers include one or more checkpoints that reference information stored in the content addressable store that defines attributes of the instance of the business service, wherein at least one checkpoint of the instance type layers includes a timestamp and a hash value associated with an entry in the content addressable store.

Abstract: Systems and methods for the identification and reconciliation of network resource information are herein disclosed. In an implementation, a system includes instructions stored in memory for processing a request received from a data source to update a record of a network resource by receiving data relating to an attribute of a network resource of a computer network from a first data source, wherein the network resource is associated with a configuration item of a configuration management database, the configuration item including data relating to the attribute from a second source; determining that the first data source is authoritative for the attribute based on a priority of the first data source, a priority of the second data source, and a staleness period of the second data source; and processing the request by updating the attribute based on the data.

Abstract: Systems and methods for the identification and reconciliation of network resource information are herein disclosed. In an implementation, a system includes instructions stored in memory for processing a request received from a data source to update a record of a network resource by receiving data relating to an attribute of a network resource of a computer network from a first data source, wherein the network resource is associated with a configuration item of a configuration management database, the configuration item including data relating to the attribute from a second source; determining that the first data source is authoritative for the attribute based on a priority of the first data source, a priority of the second data source, and a staleness period of the second data source; and processing the request by updating the attribute based on the data.

Abstract: A method for configuration management database governance comprising: identifying a first configuration item and a second configuration item; identifying a relationship between the first configuration item and the second configuration item; identifying a relationship rule governing the relationship between the first configuration item and the second configuration item; determining whether the relationship between the first configuration item and the second configuration ident is consistent with the relationship rule; and allowing, in response to a determination that the relationship between the first configuration item and the second configuration item is consistent with the relationship rule, the first configuration item and the second configuration item to be stored in the configuration management database.

Abstract: A method can include storing information about the business service in one or more template type layers; storing information about an instance of the business service in one or more instance type layers; wherein the template type layers include one or more checkpoints that reference information stored in a content addressable store that defines an expected structure of the business service, wherein at least one checkpoint of the template type layers includes a timestamp and a hash value associated with an entry in the content addressable store; and wherein the instance type layers include one or more checkpoints that reference information stored in the content addressable store that defines attributes of the instance of the business service, wherein at least one checkpoint of the instance type layers includes a timestamp and a hash value associated with an entry in the content addressable store.

Abstract: Automatically generating code used with device drivers for interfacing with hardware. The method includes receiving a machine readable description of a hardware device, including at least one of hardware registers or shared memory structures of the hardware device. The method further includes determining an operating system with which the hardware device is to be used. The method further includes processing the machine readable description on a code generation tool to automatically generate code for a hardware driver for the hardware device specific to the determined operating system.

Abstract: Systems and methods for the identification and reconciliation of network resource information are herein disclosed. In an implementation, a system includes instructions stored in memory for processing a request received from a data source to update a record of a network resource by receiving data relating to an attribute of a network resource of a computer network from a first data source, wherein the network resource is associated with a configuration item of a configuration management database, the configuration item including data relating to the attribute from a second source; determining that the first data source is authoritative for the attribute based on a priority of the first data source, a priority of the second data source, and a staleness period of the second data source; and processing the request by updating the attribute based on the data.

Abstract: Automatically generating code used with device drivers for interfacing with hardware. The method includes receiving a machine readable description of a hardware device, including at least one of hardware registers or shared memory structures of the hardware device. The method further includes determining an operating system with which the hardware device is to be used. The method further includes processing the machine readable description on a code generation tool to automatically generate code for a hardware driver for the hardware device specific to the determined operating system.

Abstract: A garbage collector includes a core, and extension handlers to support collection of objects of a designated managed class. The handler, which may be implemented in managed code, receives notification of garbage collection phases, and receives control from the core when the core encounters an object of the designated class. The handler can then thread together discovered objects of the designated class, walk a list of objects and detect whether any are unreachable, and/or provide an executor for the designated class. The core notifies handlers about progress in tracing strong pointers, tracing weak pointers, pointer update, pinning, weak pointer forwarding, and untraced pointer relocation. A pointer can be marked as untraced, so the core ignores it during pointer tracing phases. If the core encounters an object which has a weak pointer field, the core can pass control to a handler's tracing method. The core may perform generational garbage collection.

Abstract: A garbage collector includes a core, and extension handlers to support collection of objects of a designated managed class. The handler, which may be implemented in managed code, receives notification of garbage collection phases, and receives control from the core when the core encounters an object of the designated class. The handler can then thread together discovered objects of the designated class, walk a list of objects and detect whether any are unreachable, and/or provide an executor for the designated class. The core notifies handlers about progress in tracing strong pointers, tracing weak pointers, pointer update, pinning, weak pointer forwarding, and untraced pointer relocation. A pointer can be marked as untraced, so the core ignores it during pointer tracing phases. If the core encounters an object which has a weak pointer field, the core can pass control to a handler's tracing method. The core may perform generational garbage collection.

Abstract: Serialized data from broadcast services is provided to a broadcast server for transmitting to one or more client devices. The serialized data may correspond to shared data, private data, or control data. Data is scheduled for transmission based on weighted priorities including quality of service metrics. The transmission frame is arranged according to a frame protocol that includes provisions for a table of contents indexing system for the shared data. Packets of shared data are formatted based on criteria that is known by the particular broadcast service and corresponding application that is resident on the client device. The client device receives the table of contents at the transport layer, and notifies applications of data that will be available in the next frame. Applications submit prioritized requests to the transport layer, requesting data in the next frame. Data is retrieved by the transport layer, and deserialized by handlers for each application.

Abstract: A runtime execution environment may manage resources executing cooperative threading on a single physical thread. One example can scan eligible activation records linked to threads on a method process and can execute one of the activation records. This example can create a new activation record for a new method invoked for the executed activation record and link the new activation record to the executed activation record. Further, this example can loop back to re-start the method.

Abstract: In a managed code execution environment in which resources are constrained, resources may be managed in accordance with weak references for which semantics are extended.

Abstract: A runtime execution environment may implement code access security by annotating a delegate to a publisher with a list of potential callers to the publisher. If a permission verification process for at least the listed potential callers results in even one indication of no trust, an exception may be thrown.

Abstract: A system and method for providing help contents uses a framework for unified help access that provides a single point of entry through which a user may access help contents relating to all system software and hardware components. The help contents from different sources are organized into a taxonomy structure that allows a user to navigate easily to locate relevant help topics. The contents of the help topics may reside locally or be accessible over the Internet, and may contain static as well as active components. The unified help framework is extensible, allowing the help topics and the taxonomy to be updated by means of update packages. The application for providing the unified presentation of help topics may be launched by a user as well as from programs.

Abstract: Described is a system and method for searching multiple disparate search engines. More particularly, a search system provides search engine manager that operates to provide a standard interface with which one or more search engines may be queried through a search client. The search system being extensible, allows for the addition of search engines beyond the time of the initial construction of the search system. Each search engine, being wrapped around a COM (component object model) object, first registers with the search system through the wrapper, the wrapper providing communication between the search engine manager and the search engine. When initiated by a client, a query is transmitted to the search engines in series, the search engines execute the query in parallel, and the results are returned asynchronously to the client.