Distributed web services network architecture

• US 7,529,805 B2
• Filed: 10/02/2007
• Issued: 05/05/2009
• Est. Priority Date: 11/21/2001
• Status: Expired due to Fees

• Current Assignee: Akana, Inc. (Perforce Software Incorporated)
• Original Assignee: Blue Titan Software, Inc. (Perforce Software Incorporated)
• Inventors: Martinez, Frank, Toth, Paul Kevin
• Primary Examiner(s): NEURAUTER, GEORGE C
• Application Number:
  US11/866,063
• Publication Number:
  US 20080086573A1
• Time in Patent Office: 581 Days
• Field of Search: 709/211, 709/238
• US Class Current: 709/211
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Methods, apparatuses and systems facilitating deployment, configuration and maintenance of web services networks. The present invention features a distributed web services network architecture that, in one embodiment, leverages the functionality of existing network infrastructure to provide a low cost, efficient and reliable web services solution. The web services network architecture according to the present invention can be implemented across any suitable computer network, including an intranet or the Internet.

Claims

1. An apparatus, comprising:

a processor,

a memory, and

a web services routing node application comprising computer program instructions operative to cause the processor to;

maintain a routing table in the memory, the routing table including routing entity data allowing for the routing of service action requests across a computer network, the routing entity data comprising one or more action names and corresponding network resource locators;

receive service action requests including action names from subscribing nodes;

route the service action requests to respective service providing endpoints associated with the network resource locators corresponding to the action names;

receive a routing entity request from a child routing node identifying a routing entity; and

transmit a response to the child routing node operative to add the routing entity to a local routing table of the child routing node.

2. The apparatus of claim 1 wherein the web services routing node application further comprises instructions operative to cause the processor to

transmit, in response to a service action request requiring a routing entity not contained in the routing table, a routing entity request to a parent node.

3. The apparatus of claim 1 wherein the web services routing node application further comprises instructions operative to cause the processor to

transmit, in response to a routing entity request requiring a routing entity not contained in the routing table, a routing entity request to a parent node.

4. The apparatus of claim 2 wherein the web services routing node application further comprises instructions operative to cause the processor to

receive a response to the routing entity request from the parent node;

and

add routing entity information in the response to the routing table.

5. The apparatus of claim 3 wherein the web services routing node application further comprises instructions operative to cause the processor to

receive a response to the routing entity request from the parent node;

and

add routing entity information in the response to the routing table.

6. The apparatus of claim 1 wherein the web services routing node application further comprises instructions operative to cause the processor to maintain local routing table(s) of one or more child routing node(s) associated therewith.

7. The apparatus of claim 6 wherein the web services routing node application further comprises instructions operative to cause the processor to receive and process updates to routing entities in the routing table;

and responsive to the updates, update the local routing table(s) of the child routing node(s) associated therewith.

8. The apparatus of claim 1 wherein the web services routing node application further comprises instructions operative to cause the processor to establish respective connections to the service providing endpoints for transmission of the service action requests and receipt of responses to the service action requests.

9. The apparatus of claim 6 wherein the web services routing node application further comprises instructions operative to cause the processor to maintain a routing matrix, wherein the routing matrix facilitates maintenance of the local routing table(s) of the child routing node(s) associated with the parent node.

10. The apparatus of claim 9 wherein the routing matrix facilitates identification of out-of-date routing entities in the local routing table(s) of the child routing node(s).

11. The apparatus of claim 10 wherein the routing matrix contains parent node update stamps for corresponding routing entities in the first routing table;

and wherein, for each child routing node associated with the parent node, the routing matrix contains a routing node update stamp for each routing entity in the local routing table.

12. The apparatus of claim 10 wherein the web services routing node application further comprises instructions operative to cause the processor to update a routing entity in the local routing table of a child routing node based on a comparison of the corresponding parent node update stamp and routing node update stamp.

13. Logic encoded in one or more tangible media for execution and when executed operable to:

maintain a routing table in a memory, the routing table including routing entity data allowing for the routing of service action requests across a computer network, the routing entity data comprising one or more action names and corresponding network resource locators;

receive service action requests including action names from subscribing nodes; and

route the service action requests to respective service providing endpoints associated with the network resource locators corresponding to the action names,

receive a routing entity request from a child routing node identifying a routing entity;

transmit a response to the child routing node operative to add the routing entity to a local routing table of the child routing node.

14. A method comprising

maintaining a routing table in a memory, the routing table including routing entity data allowing for the routing of service action requests across a computer network, the routing entity data comprising one or more action names and corresponding network resource locators;

receiving service action requests including action names from subscribing nodes; and

routing the service action requests to respective service providing endpoints associated with the network resource locators corresponding to the action names;

receiving a routing entity request from a child routing node identifying a routing entity; and

transmitting a response to the child routing node operative to add the routing entity to a local routing table of the child routing node.

15. The method of claim 14 further comprising

transmitting, in response to a service action request requiring a routing entity not contained in the routing table, a routing entity request to a parent node.

16. The method of claim 14 further comprising

transmitting, in response to a routing entity request requiring a routing entity not contained in the routing table, a routing entity request to a parent node.

17. The method of claim 15 further comprising

receiving a response to the routing entity request from the parent node;

and

adding routing entity information in the response to the routing table.

18. The method of claim 16 further comprising

receiving a response to the routing entity request from the parent node;

and

adding routing entity information in the response to the routing table.

19. The method of claim 14 further comprising maintaining local routing table(s) of one or more child routing node(s) associated therewith.

20. The method of claim 19 further comprising receiving and processing updates to routing entities in the routing table;

and responsive to the updates, updating the local routing table(s) of the child routing node(s) associated therewith.