Search International and National Patent Collections
Some content of this application is unavailable at the moment.
If this situation persists, please contact us atFeedback&Contact
1. (WO2007011471) NODE-TO-NODE COMMUNICATION PIPELINES
Note: Text based on automatic Optical Character Recognition processes. Please use the PDF version for legal matters

WE CLAIM

1 . A method, comprising:
specifying (410) at least one parameter for a node-to-node pipeline implementation; and
accessing (420) a service (41 5) to configure a node-to-node pipeline having modules that satisfy the specified parameters in a predetermined order.

2. A method according to Claim 1 , wherein the at least one parameter includes an API of a node application.

3. A method according to Claim 1 , wherein the at least one parameter includes at least one of an API of a node application, an API of a peer application, or a protocol constraint.

4. A method according to Claim 1 , wherein the at least one parameter specifies a constraint including one of cross-isolation construct compatibility, cross-process compatibility, or cross-machine compatibility.

5. A method according to Claim 1 , wherein the pipeline includes a first node API-implemented adapter module, a second node API-implemented adapter module, and a protocol constraint module.

6. A method according to Claim 1 , wherein one node is a host application and another node is an add-in application.

7. At least one computer-readable medium having one or more computer-executable instructions that, when read, cause one or more processors to:
register (405) modules that may be used in assembling node-to-node 5 communication pipelines;
receive (41 0) at least one parameter to define a particular node-to-node communication pipeline; and
assemble (420) at least one version of the particular node-to-node communication pipeline using modules that comply with the parameter.

10 8. At least one computer-readable medium according to Claim 7, wherein the one or more instructions are executed, at least in part, at a service.

9. At least one computer-readable medium according to Claim 7, wherein the modules include at least one of a first node-to-protocol adapter module, a protocol module, and at least one protocol-to-second node protocol i s adapter module.

10. At least one computer-readable medium according to Claim 7, wherein the node-to-node pipelines are inter-protocol communication pipelines.

π . At least one computer-readable medium according to Claim 7, wherein the node-to-node pipelines are inter-protocol communication pipelines 20 to be implemented from a host-application API to an add-in application API.

12. At least one computer-readable medium according to Claim 7, wherein the at least one parameter includes at least one of an API of a first node application, an API of a second node application, or an inter-protocol constraint.

13. At least one computer-readable medium according to Claim 7, 5 wherein the at least one parameter includes an inter-protocol constraint including one of cross-isolation construct compatibility, cross-process compatibility, or cross-machine compatibility.

14. At least one computer-readable medium according to Claim 7, wherein the at least one parameter includes an inter-protocol constraint io specifying a first node in a managed execution environment communicating with a second node in an unmanaged execution environment.

1 5. At least one computer-readable medium according to Claim 7, wherein the one or more instructions to assemble cause the one or more processors to assemble the modules that comply with the parameter in a specific i s order.

1 6. A system, comprising:
a host (220) to specify one or more parameters for a specified intra- protocol pipeline;
a service (41 5) to:
20 register (405) modules that are usable in assembling intra-protocol pipelines, and assemble (420) various ones of the registered modules that satisfy the one or more parameters into one or more versions of the specified intra- protocol pipeline; and
an activator to activate (425) one or more of the assembled versions of the 5 specified intra-protocol pipeline.

1 7. A system according to Claim 16, wherein the at least one parameter includes at least one of an API of a host application, an API of an add- in application, or an inter-protocol constraint.

1 8. A system according to Claim 1 6, wherein the one or more io parameters include at least one of an inter-protocol constraint including one of cross-isolation construct compatibility, cross-process compatibility, or cross- machine compatibility.

19. A system according to Claim 1 6, wherein the specified intra- protocol pipeline includes, at least, one of a host API-to-protocol adapter, a i s protocol, and a protocol-to-add-in adapter.

20. A system according to Claim 1 6, wherein the specified intra- protocol pipeline extends from a host API in a managed execution environment to an add-in API in an unmanaged execution environment.