# US 2012/0254278 A1 · Dynamic Dispatch for Distributed Object-Oriented Software Systems

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254278 A1
- Document ID: US20120254278A1
- Status: Published application
- Kind: A1
- Application number: 13/074,540
- Filed: 2011-03-29
- Published: 2012-10-04
- Earliest claimed: 2011-03-29
- Assignees: BMC Software, Inc.
- Inventors: Jonathan Whitney; Alexander Vul; Mathew Connors; Johan Eriksson; Atanu Neogi
- Web page: https://patentgrep.com/patent/US20120254278A1

## CPC

- G06F 9/5055: {considering software capabilities, i.e. software resources associated or available to the machine}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A provider definition represents software that implements the semantics of one or more operations on an object in an object-oriented system. A provider represents a specific instance of a provider definition. One or more providers implement operations for objects in the system. A component of the system called the provider registry maintains a mapping of providers and operations as defined by the provider definitions. When handling a request to invoke a operation on an object, the system dynamically dispatches to the correct provider based on this mapping. Where more than one provider are registered as implementing the desired operation on an object, techniques are disclosed for selecting a provider to perform the desired operation.

## Claims

### Claim 1

A method of dynamically dispatching a request to perform an operation on an object in an object-oriented software system, comprising:
receiving the request from a client software, executing on a client computer;
requesting provider information from a registry of providers;
selecting by the registry of providers a first provider registered as performing the operation on the object; and
sending the request to perform the operation on the object to the first provider for execution by the first provider.

### Claim 2 (depends on 1)

The method of claim 1, wherein the provider information comprises:
a node information, corresponding to a computer associated with the provider; and
information identifying the provider and operations performed by the provider.

### Claim 3 (depends on 2)

The method of claim 2, wherein the provider information further comprises:
a provider relationship information, identifying a relationship between two providers registered in the registry of providers.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
receiving a request from the first provider to perform the operation on the object;
requesting substitute provider information from the registry of providers;
selecting by the registry of providers a second provider registered as performing the operation on the object, different from the first provider; and
sending the request to perform the operation on the object to the second provider for execution by the second provider.

### Claim 5 (depends on 4)

The method of claim 4, wherein the second provider is a child of the first provider.

### Claim 6 (depends on 4)

The method of claim 4, wherein the second provider is a peer of the first provider.

### Claim 7 (depends on 1)

The method of claim 1, wherein the act of selecting by the registry of providers a first provider registered as performing the operation on the object comprises:
identifying a plurality of providers registered with the registry of providers as performing the operation on the object; and
selecting the first provider from the plurality of providers.

### Claim 8 (depends on 7)

The method of claim 7, wherein the act of selecting the first provider from the plurality of providers comprises:
evaluating a policy to determine which of the plurality of providers should perform the operation on the object.

### Claim 9 (depends on 7)

The method of claim 7, wherein the act of selecting the first provider from the plurality of providers comprises:
requesting an advisor information from the registry of providers;
selecting by the registry of providers a third provider registering as performing a provider selection operation; and
selecting the first provider by the third provider.

### Claim 10 (depends on 7)

The method of claim 7, wherein the act of selecting the first provider from the plurality of providers comprises:
selecting the first providers from the plurality of providers randomly.

### Claim 11 (depends on 7)

The method of claim 7, wherein each provider of the plurality of providers performs the operation on the object differently than each other provider of the plurality of providers.

### Claim 12 (depends on 1)

The method of claim 1, wherein the act of requesting provider information from the registry of providers comprises:
sending a request for provider information from an application programming interface on the client computer to the registry of providers, executing on a second computer.

### Claim 13 (depends on 1)

The method of claim 1, further comprising:
registering a provider with the registry of providers as performing one or more operations on one or more objects.

### Claim 14 (depends on 1)

The method of claim 1, wherein the registry of providers comprises software executing on a provider registry computer.

### Claim 15 (depends on 1)

A computer readable medium with instructions for a programmable control device stored thereon wherein the instructions cause a programmable control device to perform the method of claim 1.

### Claim 16

A networked computer system comprising:
a provider registry, comprising:
a processor;
a provider definition datastore, coupled to the processor, comprising information corresponding to providers and operations provided by providers;
software comprising instructions that when executed by the processor cause the processor to perform actions comprising:
selecting a provider registered in the provider definition datastore as performing a first operation on a first object; and
an application program interface, callable by a client software executing on a client computer that performs actions comprising:
receiving a request from the client software to perform the first operation on the first object;
requesting provider information from the provider registry; and
sending the request to a provider selected by the provider registry.

### Claim 17 (depends on 16)

The networked computer system of claim 16, further comprising:
a provider computer, comprising:
a processor; and
a provider software, comprising instructions that when executed by the processor of the provider computer cause the processor of the provider computer to perform actions comprising:
performing a first operation on a first object,
wherein the provider software is registered by the provider registry as performing the first operation on the first object.

### Claim 18 (depends on 16)

The networked computer system of claim 16, further comprising:
a policy engine, comprising:
a processor;
a policy datastore, coupled to the processor, storing a plurality of policies;
a policy software, comprising instructions that when executed by the processor of the policy engine cause the processor of the policy engine to perform actions comprising:
receiving a request to select a provider from a plurality of providers;
evaluating one or more of the plurality of policies; and
responding to the request with a selected provider from the plurality of providers.

### Claim 19 (depends on 18)

The networked computer system of claim 18, wherein the policy software is registered in the provider registry.

### Claim 20 (depends on 18)

The networked computer system of claim 18, wherein the provider registry locates the policy engine by a provider lookup in the provider definition datastore.
