Asynchronous protocol framework
First Claim
1. A method for providing an asynchronous protocol framework, comprising the operations of:
- providing a registry having a plurality of proxies, each proxy implementing a generic interface for a related to a software component, each proxy capable of providing specific messages to the related software component based on an underlying design structure of the software component;
obtaining a first proxy from the registry, the first proxy related to a first software component; and
sending a message to the first software component using the generic interface of the first proxy, wherein the first proxy sends a specific message to the first software component based on the underlying design structure of the first software component.
3 Assignments
0 Petitions
Accused Products
Abstract
An invention is disclosed for providing an asynchronous protocol framework. A registry is provided having a plurality of proxies, wherein each proxy implements a generic interface for a related to a software component. In addition, each proxy is capable of providing specific messages to the related software component based on an underlying design structure of the software component, for example, EJB specific or JMS specific messages. A first proxy is obtained from the registry, wherein the first proxy is related to a first software component, a message is sent to the first software component using the generic interface of the first proxy. In particular, the first proxy sends a specific message to the first software component based on the underlying design structure of the first software component.
-
Citations
20 Claims
-
1. A method for providing an asynchronous protocol framework, comprising the operations of:
-
providing a registry having a plurality of proxies, each proxy implementing a generic interface for a related to a software component, each proxy capable of providing specific messages to the related software component based on an underlying design structure of the software component;
obtaining a first proxy from the registry, the first proxy related to a first software component; and
sending a message to the first software component using the generic interface of the first proxy, wherein the first proxy sends a specific message to the first software component based on the underlying design structure of the first software component. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. An asynchronous protocol framework, comprising:
-
a registry having a plurality of proxies, each proxy implementing a generic interface for a related to a software component, each proxy capable of providing specific messages to the related software component based on an underlying design structure of the software component; and
a first software component having a first underlying design structure and a related first proxy in the registry, wherein a second software component sends messages to the first software component using the first proxy. - View Dependent Claims (11, 12, 13, 14)
-
-
15. An asynchronous protocol framework, comprising:
-
a registry having a plurality of proxies, each proxy implementing a generic interface for a related to a software component, each proxy capable of providing specific messages to the related software component based on an underlying design structure of the software component, each proxy is identified using a naming convention including a domain, a type, and a session; and
a first software component having a first underlying design structure and a related first proxy in the registry, wherein a second software component sends a message to the first software component using the first proxy, and wherein the message is routed to the first software component based on a domain, type, and session specified in the message. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification