World-wide-web server with delayed resource-binding for resource-based load balancing on a distributed resource multi-node network
August 5, 2016. Estimated Expiration Date is calculated based on simple USPTO term provisions. It does not account for terminal disclaimers, term adjustments, failure to pay maintenance fees, or other factors which might affect the term of a patent.Patent ReferencesMethod and apparatus for sharing a telecommunications channel among multiple users Method and apparatus for processing multiple file system server requests in a data processing network Data processing system with data transmission failure recovery measures Parallel I/O network file server architecture System for substituting tags for non-editable data sets in hypertext documents and updating web files containing links between data sets corresponding to changes made to the tags Communications system for an ISDN and a LAN, and an ISDN-LAN connection terminal Method and apparatus for extensible object-oriented inter-application link management Data transmission routing system Network video server system receiving requests from clients for specific formatted data through a default channel and establishing communication through separate control and data channels Method for storing data in an interactive computer network InventorsApplicationNo. 691006 filed on 08/05/1996US Classes:709/201, DISTRIBUTED DATA PROCESSING709/202, Processing agent709/203, Client/server709/206, Demand based messaging709/219, Accessing a remote server709/225, Computer network access regulating709/229, Network resources access controlling709/236, Computer-to-computer data framing709/239, Alternate path routing718/100, TASK MANAGEMENT OR CONTROL718/104, Resource allocation718/105Load balancingExaminersPrimary: Lall, Parshotam S.Assistant: Barot, Bharat Attorney, Agent or FirmInternational ClassesG06F 013/00G06F 017/30 670-675 AbstractA multi-node server transmits world-wide-web pages to network-based browser clients. A load balancer receives all requests from clients because they use a virtual address for the entire site. The load balancer makes a connection with the client and waits for the URL from the client. The URL specifies the requested resource. The load balancer waits to perform load balancing until after the location of the requested resource is known. The connection and URL request are passed from the load balancer to a second node having the requested resource. The load balancer re-plays the initial connection packet sequence to the second node, but modifies the address to that for the second node. The network software is modified to generate the physical network address of the second node, but then changes the destination address back to the virtual address. The second node transmits the requested resource directly to the client, with the virtual address as its source. Since all requests are first received by the load balancer which determines the physical location of the requested resource, nodes may contain different resources. The entire contents of the web site is not mirrored onto all nodes. Network bottlenecks are avoided since the nodes transmit the large files back to the client directly, bypassing the load balancer. Client browsers can cache the virtual address, even though different nodes with different physical addresses service requests.Other References
| |
