Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS6598077 B2
Publication typeGrant
Application numberUS 09/730,259
Publication dateJul 22, 2003
Filing dateDec 5, 2000
Priority dateDec 6, 1999
Fee statusLapsed
Also published asUS20010039586, US20030158951, WO2001044894A2, WO2001044894A3
Publication number09730259, 730259, US 6598077 B2, US 6598077B2, US-B2-6598077, US6598077 B2, US6598077B2
InventorsLeonard Primak, Kailai Chen, John Gnip
Original AssigneeWarp Solutions, Inc.
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
System and method for dynamic content routing
US 6598077 B2
Abstract
A system for directing a request for dynamic content to an application server which having access to a database containing updated data relevant to the request. The system contains a dynamic content router, database replication agents and web server plug-ins. The dynamic content router directs the web server plug-ins to forward the request to the appropriate application server.
Images(6)
Previous page
Next page
Claims(14)
What is claimed:
1. A method of dynamic content routing a client request to an application server, comprising the steps of:
receiving a plurality of requests for dynamic content from a client associated with a session over a communications network, wherein at least one of said requests includes a content label;
determining whether a request received from said client includes said content label;
associating said content label with said session and said client if it is determined that said request received from said client includes said content label;
selecting an application server group from a plurality of application servers in accordance with said content label associated with said session;
routing all requests received from said client to said selected application server group;
determining a session ID and a session time of said session;
associating said content label associated with said session to said session ID to provide a link; and
storing said link, said session ID and said session time as a last session time.
2. The method of claim 1, wherein the step of selecting includes the step of selection an application server group based on session persistence.
3. The method of claim 1, further comprising the steps of:
reading said session ID from said request to determine said link if it is determined that said request received from said client does not include said content label; and
determining said content label as a function of said link.
4. A method of dynamic content routing a client request to an application server, comprising the steps of:
receiving a plurality of requests for dynamic content from a client associated with a session over a communications network, wherein at least one of said requests includes a content label;
determining whether a request received from said client includes said content label;
associating said content label with said session and said client if it is determined that said request received from said client includes said content label;
selecting an application server group from a plurality of application servers in accordance with said content label associated with said session; and
routing all requests received from said client to said selected application server group
storing said selected application server group as a last accessed server group wherein each application server group being associated with a database;
determining replicaton latencies between said databases; and
storing said replicaton latencies.
5. The method of claim 4, wherein the step of selecting includes the step of selecting an application server group as a function of said replication latencies.
6. The method of claim 4, wherein the step of selecting includes the steps of:
determining time elapsed between said last session time and a current session time if the database connected to said selected application server group is different from the database connected to said last accessed server group for said client to provide a session interval; and
selecting said last accessed server group as said selected application server group if said replication latency between the databases connected to said last accessed server group and said selected application server group exceeds said session interval.
7. A system for dynamic content routing a client request to an application server comprising:
a web server for receiving a plurality of requests for dynamic content from a client associated with a session over a communications network, wherein at least one of said requests includes a content label;
a dynamic content router for determining whether a request received from said client includes said content label, associating said content label with said session and said client if it is determined that said request received from said client includes said content label, and selecting an application server group from a plurality of application servers connected to said network in accordance with said content label associated with said session;
wherein said web server is operable to route all requests from said client to said selected application server group; and
wherein said router is operable to determine a session ID and a session time of said session, associate said content label associated with said session to said session ID to provide a link, and store said link, said session ID and said session time as a last session time.
8. The system of claim 7, wherein said router is operable to select an application server group based on session persistence.
9. The system of claim 7, wherein said router is operable to read said session ID from said request to determine said link if it is determined that said request received from said client does not include said content label and determine said content label as a function of said link.
10. A system for dynamic content routing a client request to an application server comprising:
a web server for receiving a plurality of requests for dynamic content from a client associated with a session over a communications network, wherein at least one of said requests includes a content label;
a dynamic content outer for determining whether a request received from said client includes said content label, associating said content label with said session and said client if it is determined that said request received from said client includes said content label, and selecting an application server group from a plurality of application servers connected to said network in accordance with said content label associated with said session; and
wherein said web server is operable to route all requests from said client to said selected application server group;
wherein said route is operable to store said selected server group as a last accessed server group;
wherein each application server group being associated with a database; and
wherein each database includes a replication agent for determining replication latencies between said databases and transmitting said replication latencies to said router; and wherein said router is operable to store said replication latencies.
11. The system of claim 10, wherein said router is operable to select an application server group as function of said replication latencies.
12. The system of claim 10, wherein said router is operable to determine time elapsed between said last session time and a current session time if the database connected to said selected server group is different from the database connected to said last accessed server group or said client to provide a session interval, and operable to select said last accessed server group as said selected server group if said replication latency between the databases connected to said last accessed server group and said selected server group exceeds said session interval.
13. A method of dynamic content routing a client request to an application server, comprising the step of:
receiving a plurality of requests for dynamic content from a client associated with a session over a communications network, wherein at least one of said requests includes a content label;
determining whether a request received from said client includes said content label;
associating said content label with said session and said client if it is determined that said request received from said client includes said content label;
selecting an application server group from a plurality of application servers in accordance with said content label associated with said session;
routing all requests received from said client to said selected application server group
determining whether another request received from said client includes a new content label;
associating said new content label with said session and said client if it is determined that said other request received from said client includes said new content label; and
selecting an application server group from said plurality of application servers in accordance with said content label associated with said session.
14. A system for dynamic content routing a client request to an application server comprising:
a web server for receiving a plurality of requests for dynamic content from a client associated with a session over a communications network, wherein at least one of said requests includes a content label;
a dynamic content router for determining whether a request received from said client includes said content label, associating said content label with said session and said client if it is determined that said request received from said client includes said content label, and selecting an application server group from a plurality of application servers connected to said network in accordance with said content label associated with said session;
wherein said web server is operable to route all requests from said client to said selected application serve group; and
wherein said router is operable to determine whether another request received from said client includes new content label, to associated said new content label with said session and said client if it is determined that said other request received from said client includes said new content label, and to select an application server group from said plurality of application servers in accordance with said content label associated with said session.
Description
RELATED APPLICATION

This application is a continuation-in-part of U.S. provisional patent application Ser. No. 60/241,528, filed Oct. 17, 2000; a continuation-in-part of patent application Ser. No. 09/565,259, filed May 5, 2000, now U.S. Pat. No. 6,389,448, which is a continuation-in-part of U.S. provisional patent application Ser. No. 60/169,196, filed Dec. 6, 1999; a continuation-in-part of U.S. provisional patent application Ser. No. 60/201,801, filed May 4, 2000; and a continuation-in-part of U.S. provisional patent application Serial No. 60/202,329, filed May 5, 2000. Each of these applications are hereby incorporated by reference in their entirety.

FIELD OF THE INVENTION

The present invention generally relates to the field of website infrastructure development. Specifically, the present invention relates to a system and method for scaling website databases and directing requests for dynamic content.

BACKGROUND OF THE INVENTION

Many of today's commercial websites utilize a three layer architecture consisting of: (1) a web server layer, (2) an application server layer, and (3) a database layer. The web server layer typically has one or more web server clusters, each web server cluster having a plurality of web servers. In the three layer architecture, the web servers generally store stagnant data or content, such as HTML scripts and Java code, which is transmitted to a client's computer in response to the client's request for such stagnant content. However, when a client requests dynamic content that must be generated in real-time, the web-server issues a request to an application server within the site's application server layer for such dynamic content.

The application server layer comprises one or more application server clusters, each cluster having one or more applications servers. The application servers provide dynamic content based on information relating to or received from a specific client. That is, the application server can provide the dynamic content based on either a client's specific request, i.e., information inputted onto an input screen by the client, or the client information previously stored in a database in the site's database layer. The client information stored in the database layer can include client's personal or financial information provided by the client during his/her prior visit to the web site, information regarding the client's past activity on the website, or information relating to transactions consummated by the client on the site. For example, the database layer of a web site operated by a bank or financial institution can store information regarding the activity within and status of accounts maintained by a client of the bank.

Web servers, application servers, and databases typically communicate with one another using standard communication protocols, such as TCP/IP. However, some application server vendors have adopted proprietary communications protocols for their application servers, thereby posing potential interoperability problems in connecting to other vendors' web servers and databases.

As web site traffic grows, the site's infrastructure must be easily scalable to accommodate the increasing load on the servers and databases. For example, a system for scaling server clusters is delineated in applicant's U.S. patent applications Ser. No. 09/565,259, now U.S. Pat. No. 6,389,448 and U.S. Provisional Patent Applications No. 60/169,196, No. 60/201,810 and No. 60/202,329, each of which are herein incorporated by reference in their entirety. It is appreciated that scaling of an application server is vendor dependent and some application servers may rot scalable. However, databases are not currently easily scalable and the web site owner has limited options when the database is overloaded. When the web site database server has reached its limits in accepting and processing the number simultaneous connections, the web site owner currently has two options available for increasing the capacity of the database server. The first option is to replace the existing database or database system with a higher capacity database or database system and the second option is to add another database and appropriately modify the application servers (i.e., applications running on the application servers) to recognize the new database. However, both of these options are costly and complicated propositions for web site owners and/or operators. Additionally, the second option requires communized code for the application servers. Further, it is appreciated that these two options offer only short term solutions to the problem and the web site owners and/or operators may potentially face this problem along with its associated cost to correct the problem when the database again reaches its capacity limit.

Typically, Internet related applications use a client/server model, wherein a client sends its request to the server via the Internet or other comparable communications or computer network. The server processes the request, often involving accessing and changing the dynamic content related to the client, and sends the results back to the client. The server's ability to identify the dynamic content involved in the client requests is crucial to the performance of many Internet applications. This identification is not trivial since in many cases the client request contains incomplete or no information about the dynamic content. Only the server or content source has the whole knowledge about the content involved. Accordingly, the present invention provides a system and method for identifying the dynamic content involved in every client request requiring access to the dynamic content.

OBJECT AND SUMMARY OF THE INVENTION

Therefore, it is an object of the present invention to provide a system and method that overcomes the shortcomings of the prior art system.

Another object of the present invention is to provide a system and method which scales web site databases.

A further object of the present invention is to provide a system and method which directs a client's request for dynamic content or data to an application server connected to a database having the most current version of such data.

Still another object of the present invention is to provide a system and method as aforesaid, which balances load among the application servers.

In accordance with one embodiment, the present invention comprises a dynamic content router, database replication agents, and plug-ins integrated into the web servers. The web server plug-ins intercept and direct a client's request for dynamic content to the dynamic content router. The dynamic content router then determines the appropriate application server or application cluster for the client's request based on number of factors, including but not limited to the content availability, data server's capacity and session persistence. The dynamic content router transmits or forwards the identity of the selected application server to the web server plug-in, which causes the client's request to be forwarded or routed to the selected application server. However, if a session already exists between the client and one of the application servers, the dynamic content router routes all requests to such application server.

Once the web server plug-in receives the identity of the selected application server, the web server plug-in causes its associated web server to establish a connection with the selected application server. Upon establishing a connection with the web server, the selected application server initiates a session by generating and transmitting a cookie or other comparable session identifier to the web server. The web server forwards the cookie or session identifier to the client's computer for storage.

When a session is established between the client and the selected application server, the dynamic content router examines the session communications to determine or extract a client identifier (also referred to herein as a content identifier). The dynamic content router utilizes the content identifier to determine if the client is already logged onto one of the application servers on the site. If the dynamic content router determines that the client had previously logged onto one of the application servers on the web site, the dynamic content router verifies whether client's previous login information is available to the selected application server. If the client's current application server does not have access to the client's login information, then the dynamic content router directs the web server plug-in to establish a connection with an application server that has access to the client's login information.

In accordance with an embodiment of the present invention, the system additionally includes an application server proxy that acts as an interface between the web servers and application servers utilizing proprietary communications protocols.

In accordance with another embodiment of the present invention, the dynamic content router is scalable. For example, when the web site operator and/or owner adds another dynamic content router when the capacity of the existing dynamic router is exceeded, the web server plug-ins of the present invention automatically selects a least loaded dynamic content router for routing the client's requests.

Various other objects, advantages, and features of the present invention will become readily apparent from the ensuing detailed description, and the novel features will be particularly pointed out in the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The following detailed description, given by way of example, and not intended to limit the present invention solely thereto, will best be understood in conjunction with the accompanying drawings in which:

FIG. 1 is a diagram of a web site employing a three layer architecture and a dynamic content router in accordance with an embodiment of the present invention;

FIG. 2 is a diagram showing communications flow between a web server plug-in and the dynamic content router in accordance with an embodiment of the present invention;

FIG. 3 is a diagram showing communications flow between database replication agents, application server load balancing agents and the dynamic content router in accordance with an embodiment of the present invention;

FIG. 4 is a diagram showing an example of data tables maintained within the dynamic content router in accordance with an embodiment of the present invention; and

FIG. 5 is a diagram of a website employing a three layer architecture, multiple dynamic content routers and application server proxies in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention is readily implemented using presently available communication and computing apparatuses and electronic components. The invention finds ready application in private or public communications networks, including but not limited to the Internet, a computer network, a wireless network, a satellite network, a cable network or any other form of network capable of transporting data locally or globally.

Turning now to FIG. 1, there is illustrated an example of a web site 100 having a three layer architecture and a dynamic content router 10 in accordance with an embodiment of the present invention. The web site 100 has two overlapping web server clusters 110 and 120. The web server cluster 110 comprises web servers 20 a to 20 e and the second web server cluster comprising web servers 20 d to 20 g. Additionally, there are two application server clusters 130 and 140. The application server cluster 130 comprises application servers 30 a to 30 c and the application server cluster 140 comprises servers 30 d to 30 g. The application server clusters 130 and 140 are respectively connected to a separate mirrored database 40 a and 40 b. The databases 40 a and 40 b continuously replicate data tables from one to another, thereby synchronizing and maintaining a mirrored configuration.

In accordance with an embodiment of the present invention, the dynamic content are divided, classified or categorized into two classes of content: segmentable and non-segmentable content. Content is considered or classified as segmentable content if the content can be divided into small segments, each segment being self-contained and preferably represented by a content label. Operations or operational tasks can be associated with a particular content label, wherein such associated operations are performed only on or affect only the content segments corresponding to the content label. That is, the dynamic content of the client can be represented by a content label. Preferably, the content label can be used in one of the client requests to obtain the authentication to determine if the client has previously accessed the web site or the application server. For example, the system can authenticate or determine if the client had previously accessed the web site or the application server during the login or sign in process before the client can initiate any transaction or request for content.

Whereas, content is considered or classified as non-segmentable content if the content cannot be represented by a content label or shared by one or more segments of the segmentable content. The segmentable dynamic content can be mirrored because different people can access different segments of the segmentable content at the same time while maintaining data integrity.

In accordance with an aspect of the present invention, the mirrored content can be active at the same time while maintaining its transactional integrity. For example, in a trading application, content such as the cash balance, transactions, holdings of an account can be labeled as an account, and operations or operational tasks, such as trading, depositing and withdrawing affect only content segments labeled or represented by the content label “account”. In the trading application example, the segmentable content can represent cash balances, transactions, account holdings, personal information, etc., and non-segmentable content can represent data shared by all account, such as margin rate, stock quotes, bond prices, and the like. content.

In accordance with an embodiment of the present invention, the content can be segmented or divided in number of different ways to maximize the number of mirrored content or data. That is, the present invention segments the content to maximize the number of the segmentable content, thereby effectively increasing the level or degree of mirroring for such content. Accordingly, the content stored in database 40 a and 40 b is segmentable and are represented by their content label.

In an auction site example, the segmentable content can represent either account related content or bid items. It is appreciated that if the content is segmented in one manner, i.e., based on account related content, then the system will categorize the bid items as non-segmentable content. Accordingly, the system cannot mirror all potentially “segmentable” content, i.e., the system can mirror account related content or bid items, but not both. However, it is appreciated that for a typical auction site, the number of bid item related content will far exceed the number of account related content. Also, the bid item related content is more likely susceptible to dynamical changes. Accordingly, in the auction example, the system should segment the web site data or content based on bid item rather than account data, thereby mirroring the bid item related content. The account related content can be stored in a shared database or mirrored if the system does not permit the account related content to be dynamically changed after client signs in, i.e., establishes a session.

In accordance with an aspect of the present invention, the segmentable content can be grouped into content groups, each content label belonging to one or more content group. Accordingly, operations to be performed on a group of segmentable content can be represented by content group label. The non-segmentable content can be stored in a shared database, thereby advantageously permitting the system of the present invention to provide a combination of distributed and mirrored solutions to accommodate the needs of the current and future Internet related applications.

Typically, most Internet related applications use a client/server model, wherein a client sends its request to the server via the Internet or other comparable communications or computer network. The server processes the request, often involving accessing and changing the dynamic content related to the client, and sends the results back to the client. The server's ability to identify the dynamic content involved in the client requests is crucial to the performance of many Internet applications. This identification is not trivial since in many cases the client request contains incomplete or no information about the dynamic content. Only the server or content source has the whole knowledge about content involved. Accordingly, the present invention provides a system and method for identifying the dynamic content involved in every client request requiring access to the dynamic content.

According to an embodiment of the present invention, the system and method examines the request to identify or determine the dynamic content that needs to be accessed by the request. That is, the system intercepts and examines every client request and the examination can occur before the requests reach one of the application servers 30 a to 30 g or within one of the web servers 20 a to 20 g. By building a dynamic picture of the sessions and content, the present system is able to identify the content label involved in all client requests requiring access to the dynamic content. This advantageously enables the system to know the dynamic content required for each request before such request is routed to the appropriate application server and the database. In other words, the client request can be identified by its content label before the request is routed to the appropriate database 40 a or 40 b.

After a client 60 accesses one of the application servers 30 a to 30 g for the first time, that application server assigns and maintains a session ID for the client 60. Thereafter, every client request from the client 60 includes the session ID and the application server uses the session ID to identify the client 60. Preferably, the dynamic content router saves the session ID in the session table 12 (FIG. 4). During the session, at least one of the client request includes the content label for authentication to verify that the client (or user) has access rights or privileges to the requested content. The web server extracts the content label and forwards the extracted content label to the dynamic content router 10 which stores the extracted content label in the content table 14 (FIG. 4). Preferably, the dynamic content router 10 (FIG. 1) establishes or builds a link between the session ID and the content label. It is appreciated that the subsequent client requests may or may not include the content label. However, since the client request includes session ID, the dynamic router 10 can extract the session ID from the client request. The extracted session ID then can be used by the dynamic router 10 to search the session table 12 to find corresponding content label. That is, once the session ID is found in the session table 12, the dynamic content router can use the link to locate the content label associated with this client and thereafter determine the dynamic content based on the content label.

In accordance with an embodiment of the present invention, the dynamic content router 10 uses the information extracted and/or derived from the request to route the request to the appropriate application server. For example, if the content is partitioned, by determining or knowing the dynamic content involved in the request, the dynamic content router 10 can route the request to the right source of the content, i.e., the appropriate application server. If the content source is mirrored, i.e., mirrored database, by determining or knowing the dynamic content involved in the client request, the dynamic content router 10 can identify which source of the content (or the database) has the most recent version of the content as described herein. Thus, the dynamic content router 10 of the present invention can always route the client requests to the right content source (the appropriate database). It is appreciated that the dynamic content router 10 of the present invention can be used in many Internet related applications to dynamically route the client requests based on the content associated with such requests.

Returning to FIG. 1, the client 60 sends a request for content to one of the web servers 20 a to 20 g, referred to hereinafter as the receiving web server 20. When the client 60 requests stagnant content, the receiving web server 20 provides the client 60 with the requested stagnant content. However, if the client 60 requests dynamic content, a plug-in 22 (FIG. 2), which is integrated into each web server, routes or directs the request from the client 60 to the dynamic content router 10. The dynamic content router 10 evaluates the request and selects an application server 30 based on its evaluation of the request. Also, the dynamic content router 10 sends an instruction to the plug-in 22 of the web server 30 to direct all request from the client 60 to the selected application server 30.

Turning now to FIG. 2, there is illustrated an example of the plug-in 22 of the web server 30 transmitting the request for dynamic content from the client 60 to the dynamic content router 10 and then to an application server 30 selected by the dynamic content router 10. Based on its review or evaluation of the request, the dynamic content router 10 selects an appropriate application server 30 that is best suited to provide the requested content or data to the client 60. For example, in FIG. 2, the dynamic content router 10 selects the application server 30 c based on its evaluation of the request, and informs the plug-in 22 b of the web server 20 b to direct or route all requests from the client 60 to the application server 30 c. As shown in FIG. 2, the application server 30 c is connected to the database 40 a and is part of the application server cluster 130.

Turning now to FIG. 3, there is illustrated an embodiment of the application server 32 which includes a load agent 32. That is, the application server 30 a-30 g respectively includes load agents 32 a-32 g. Each load agent 32 monitors various performance parameters of its respective application server 30, including but not limited to CPU load, disk usage, and other factors which can affect the application server's ability to receive and process requests. Additionally, each load agent 32 intermittently transmits information regarding its respective application server's ability to accept requests or connections (i.e., available capacity of the application server) to the dynamic content router 10. The dynamic content router 10 stores the available capacity information, such as in an application server load table 18 of FIG. 4.

In accordance with an embodiment of the present invention, the databases 40 a and 40 b respectively includes replication agents 42 a and 42 b for monitoring two-way replication between the databases 40 a and 40 b. Alternatively, the replication agents 42 can reside in a separate host or server to monitor any number of databases. For example, the replication agents 42 send and receive timestamp messages to and from each other. The replication agents 42 can determine the real time replication latency between databases 40 by comparing the sent and received timestamps. That is, the replication agents 42 can determine how long it takes to update data from one database 42 to another database 42 by comparing the sent and received timestamps. Each replication agent 42 reports or transmits its respective latency information to the dynamic content router 10. Preferably, the dynamic content router 10 stores the latency information for each database 40, such as in the database replication latency table 16 of FIG. 4. According to an aspect of the present invention, the replication agents 42 can also detect and report database 40 failures to the dynamic content router 10. This enables the dynamic content router 10 to isolate the disabled or failed database. For example, if the database 40 a is disabled, then the dynamic content router 10 can instruct the plug-ins 22 to route all requests for content to the application server cluster 140 which is connected to the database 40 b. That is, the requests are no longer routed to the application server cluster 130 that is connected to the disabled database 40 a.

In accordance with an embodiment of the present invention, each replication agent 42 creates a special table in the host database 40, i.e., the database being monitored by the replication agent 42. Similar to the data tables utilized by the application server 30, the special table is also replicated between the databases 40. For example, when a replication agent periodically inserts or updates a record in the special table with a replication agent identifier and a current timestamp, such updates are replicated to other databases. Also, each replication agent 42 registers a procedure, such as activating an SQL statement in the database, to monitor any change in the special table. The replication agent 42 calculates and reports the latency to the dynamic content router 10 if there is any change or update to the special table. If there is a failure with the updates, the replication agent 42 retries the procedure to determine if the database 40 is disabled or out of service. If the retries and reconnections to the database 40 are unsuccessful, the replication agent 42 reports such failure to the dynamic content router 10.

Preferably, the replication agents 42 run in the same host computer as the database 40, thereby insuring that faulty alarms are generated only when database 40 is disabled and minimizing the possibility of the faulty alarms resulting from a network failure.

In accordance with an embodiment of the present invention, as shown in FIG. 4, the dynamic content router 10 maintains four data tables: a session table 12, a content table 14, a database replication latency table 16 and an application server load table 18. In accordance with an aspect of the present invention, each record in the session table 12 has at least three fields: a session ID, a content ID and a session server ID. When an application server 30 establishes a session with a client 60, the application server 30 generates and transmits a session identifier (or a session ID) to the client 60. For example, the session ID can be a cookie or some other unique code for identifying the client 60 by the application server 30. During the session, all subsequent requests from the client 60 generally include the session ID.

Using FIG. 2 as an example, when a request is received by the web server 20 b from the client 60, the plug-in 22 b of the web server 20 b transmits the request to the dynamic content router 10. The dynamic content router 10 extracts or intercepts the session ID from the request, and stores the session ID and a session server identifier (or a session server ID) as a record in the session table 12. The session server ID identifies the application server 30 c that established the current session with the client 60 and issued the session ID.

Each time a request for content is received from the client 60, the dynamic content router 10 examines the header of the request for a session ID. If the request contains a session ID, the dynamic content router 10 compares the session ID against the entries in the session table 12. If the session ID of the request matches a session ID in one of the session records stored in the session table 12, the dynamic content router 10 instructs the plug-in 22 b to route the request to the application server associated with the session server ID in the matching session record. However, if no matching session record is found, the dynamic content router 10 selects an application server based on some criteria, such as available capacity, access to a database containing the requested data, randomly, etc.

In accordance with an embodiment of the present invention, the dynamic content router 10 selects an application server 30 based on load values stored in the application server load table 18. The dynamic content router 10 compares the load value of each application server 30 to determine which application server 30 has available capacity to process the request from the client 60. For example, the dynamic content router 10 selects an application server 30 having the lowest load, thereby directing or routing the request to the application server 30 having the highest available capacity. If the total capacity of each application server 30 varies, the dynamic content router 10 can select an application server 30 having the lowest load value relative to other application servers 30.

After a session is established between a client 60 and the selected application server 30, the user associated with the client 60 (collectively referred to herein as the client) client or user can provide his/her identity through a login or signing in process, e.g., entering a name and password onto a login screen. For example, the web site operator/owner can institute a login process to limit access to its web site to only authorized users. The content label, e.g., identification of user, client, gateway, ISP, etc., is identified in this process and the unique content id is assigned to the content label that identified the content segment. The request containing the content ID is also forwarded to router 10 by plug-in 22. The router 10 stores the Content ID along with the associated Session ID and Session Server ID in the Session Table 12.

During the login process, the plug-in 22 of the web server 20 identifies the content label of the request, i.e., the identity of the client. Each content label is uniquely associated with a content ID. The plug-in 22 forwards the request and the content ID to the dynamic content router 10 which stores the content ID along with the associated session ID and session server ID in the session table 12.

Each time a client 60 logs onto the web site, the plug-in 22 of the web server 20 sends the content ID of the client 60 to the dynamic content router 10. The dynamic content router 10 compares the content ID of the client 60 against the entries in the content table 14. If no matching content record is found in the content table 14 indicating that the client is a first time visitor of the web site, the dynamic content router 10 generates a new content record for the client 60 in the content table 14. The new content record contains at least the content ID of the client 60, the session server ID stored in the “last access server” field in FIG. 4, and the login time and date of the client stored in the “last access time” field in FIG. 4.

If the client 60 had previously logged onto the web site, then one of the content records in the content table 14 will contain the content ID of the client 60. Accordingly, on each subsequent visit to the web site by the client 60, the dynamic content router 10 locates the content record of the client 60 from the content table 14. The content record of the client 60 includes the time and date of the client's last login or session and the identification of the application server 30 accessed by the client 60 in the last login (or the last accessed application server). If the client's current session server is same as the last accessed application server, the dynamic content router 10 updates the “last access time” field of the client's content record with the client's current session or login time and date.

However, if the client's current session server is different from the last accessed application server, the dynamic content router 10 determines whether the client's requests can be processed by the current session server or routed to another application server 30. The dynamic content router 10 reads the database replication latency table 16 to compare the replication latency values of the database connected to the client's current session server and the database connected to the last accessed application server. If the replication latency of the two databases 42 a and 42 b (the period of time it takes to copy updated records from one database to the other) is less than the time elapsed between the client's last access time and the client's current login time (i.e., a session interval), the dynamic content router 10 determines that the current session server can process the client's requests and appropriately updates the last accessed application server field and the last access time field of the client's content record. That is, the last accessed application server field now identifies the current session server and the last access time now reflects the client's current login time and date. It is appreciated that if the client's current session server and the last accessed server are connected to the same database 40, then the replication latency value will be zero and the dynamic content router 10 maintains the selection of the current session server and appropriately updates the last accessed application server field and the last access time field of the client's content record.

If the replication latency of the two databases 42 a and 42 b is greater than the time elapsed between the client's last access time and client's current login time, the dynamic content router 10 terminates the session with the client's current session server and establishes a new session with the last accessed application server, thereby creating a new session server for the client 60. That is, the dynamic content router 10 instructs the plug-in 22 to route the client's requests to the new session server (the last accessed application server) instead of the current session server. In accordance with an embodiment of the present invention, the dynamic content router 10 establishes the new session with the last accessed application server by sending the original request (which was saved when a session was first established with the current session server) to the last accessed application server and capturing the set session response, i.e., a response, such as a html page, from the last accessed application server. The dynamic content router 10 sends the set session response to the plug-in 22, which forwards it to the client 60. Thereafter, the client 60 includes the new session ID in its requests. Once the plug-in 22 facilitates the establishment of a new session between the client 60 and the new session server 30 (the last accessed application server), the dynamic content router 10 updates the last access time field of the client's content record to reflect the client's current login time and date. The dynamic content router 10 also updates the session table 12 to identify the client's new session server and to indicate the session ID issued by the new session server 30 for the client 60.

The database replication latency table 16 contains records indicating the replication latency between any pair of databases 40 on the web site. The replication agents 42 residing in each database 40 updates the database replication latency table 16.

Turning now to FIG. 5, there is illustrated an example of a website 100 employing multiple dynamic content routers 10 and application server proxies 50 a and 50 b to handle proprietary protocol of the application servers 30 in accordance with the present invention. When a client 60 transmits a request for dynamic content, such as a request for a web page showing the client's account information stored on the site's databases 40, the request is first received by one of the web servers 20 a-20 g. For example, if the client's request is received by the web server 20 e, then the plug-in 22 e of the web server 20 e transmits the request to one of the dynamic content routers 10 a to 10 c. Preferably, the plug-in 22 e selects the dynamic content router 10 based on load information transmitted by load agents 150 a to 150 c residing and running on the dynamic content routers 10 a to 10 c, respectively. That is, the plug-in 22 e selects the dynamic content router 10 with the lowest load. For example, the plug-in 22 can select the dynamic content router 10 c as having the lowest load. It is appreciated that the tables 12, 14, 16 and 18 residing in each of the dynamic content routers 10 a to 10 c are continuously replicated, thereby maintaining the mirrored state of the dynamic content routers 10 a to 10 c.

The selected dynamic content router 10 c examines the request from the client 60 for a session ID. Since a first request from a client who has not yet established a session with one of the application servers 30 does not include a session ID, the selected dynamic router 10 c selects an application server based on load values of the application servers 30 stored in the application server load table 18 (FIG. 4). For example, the dynamic content router 10 c can select the application server 30 a belonging to the application server cluster 130 as having the lower load value. In such case, the dynamic content router 10 c instructs the plug-in 22 e to route the client's request to the application server cluster 130 via the application server proxy 50 a. The plug-in 22 e sends the client's request to the application proxy 50 a using standard TCP/IP protocols. The proxy 50 a converts the request to conform to the proprietary protocol utilized by the application servers 30 a to 30 c belonging to the application cluster 130 and forwards the request to the selected application server 30 a. In response to the request, the application server 30 a establishes a session with the client 60 and sends back a session ID to the client 60. Before the session ID reaches the client 60, the plug-in 22 e intercepts the session ID and sends a copy of the session ID to the dynamic router 10 c. The dynamic router 10 c generates a session record in its session table to record or store the session ID and the session server ID.

Subsequent requests from the client 60 may necessarily not be received by the web server 20 e. For example, if the web server 20 b receives the second request bearing the session ID issued by the application server 30 a from the client, the plug-in 22 b sends the request to the dynamic content router 10 a (currently the least loaded dynamic content router). Since all of the dynamic content routers 10 are mirrored, the session record previously generated by the dynamic content router 10 c is available from any dynamic content router's session table. That is the session table residing in the dynamic content router 10 a contains all of the session records generated by the dynamic content routers 10 a to 10 c. The dynamic content router 10 a compares the session ID in the client's request against the entries in its session Table 12. If a matching session record is found the dynamic content router 10 a instructs the plug-in 22 b to route the request to the application server 30 corresponding to the session server ID of the matching session record namely the application server 30 a in this case.

Once the client 60 logs onto the web site, and a content ID, such as a user id, is issued to the client, the dynamic content router 10 a checks its content table 14 to determine if the client 60 is a return visitor or a first time visitor. If it is determined that the client 60 is a return visitor (i.e., a matching content record exists), then the dynamic content router 10 a obtains the last accessed server information from the matching content record. However, if it is determined that the client 60 is a first time visitor (i.e., no matching content record exists), then the dynamic content router 10 a inserts a new content record for the client 60 into the content table 14. It is appreciated that the dynamic content router 10 a does not direct the plug-in 22 b to make any change with respect to the client's session with the application server 30 a since this new client 60 is not being transferred to any last accessed application server.

In accordance with an embodiment of the present invention, the application server 30 stores information relating to the client's activity on the web site (e.g., stock or money transfer information) in the database 40. Preferably, either during or shortly after the client's visit to the web site, the activity data stored in one database 40 is replicated to other database 40, e.g., activity data stored in the database 40 a is replicated to the database 40 b. It is appreciated that the activity data of the client 60 may not have been replicated to all of the databases 40 by the time the client 60 re-logs onto the web site again. The replication of the activity data depends on the replication latency between the databases 40 and the time elapsed between the client's logins.

When a client 60 is a return visitor to the web site, a content record containing the unique content ID of the client exists in each content table 14 of the dynamic content routers 10. When a returning visitor (the client 60) initiates the login process, the plug-in 22 of the web server 20 extracts the content ID corresponding to a content label from the login request. For example, the content label can be a field name assigned by an application. For example, the content label can represent an account number for a trading application and a login id for an e-commerce site application. In accordance with an embodiment of the present invention, the content label has an associated value that is assigned during the login process. For example, an account number “XF456” is associated with the account number label and login name “kchen” can be associated with the login id label. Once the content ID is extracted from the request, the dynamic content router 10 searches the mirrored content table 14 for a content record matching or containing the content ID of the client. If a matching content record is found, the dynamic content router 10 compares the client's current session server to the last accessed server information in the matching content record. For example, if the client's current session server is the application server 30 f and the last accessed server is the application server 30 a (i.e., there is a mismatch of session servers), the dynamic content router 10 accesses its database replication latency table 16 to compare the latency between the databases 40 to the time elapsed between the client's last access time and the client's current login time. If the latency is less than the elapsed time between client's logins, the dynamic content router 10 updates the last access time and the last accessed server fields of the client's content record to reflect the client's current session server and current login time. However, if the latency is greater than the elapsed time between the client's logins, the dynamic content router 10 directs the plug-in 22 which sent the content ID to the dynamic content router 10 to facilitate a new session between the client 60 and the last accessed server. Once the new session is established, the dynamic content router 10 updates the last access time field in the content record of the client to reflect the client's new login time.

In accordance with an embodiment of the present invention, the content can be updated on database server 40 a or 40 b directly (bypassing the web servers 20 and the application servers 30). In such case, the updated content information must be forwarded to the dynamic content routers 10 so they can appropriately update their content tables and correctly route the requests to the appropriate database 40. The updates are identified by content labels or group content label. Preferably, a utility process (not shown) is used directly update the database 40 and to communicate with the dynamic content router 10.

While the present invention has been particularly described with respect to the illustrated embodiment, it will be appreciated that various alterations, modifications and adaptations may be made based on the present disclosure, and are intended to be within the scope of the present invention. It is appreciated that each server and/or database can be replicated for redundancy and robustness. It is intended that the appended claims be interpreted as including the embodiment discussed above, the various alternatives that have been described, and all equivalents thereto.

Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US4748558May 1, 1986May 31, 1988Hitachi, Ltd.Load balancing control method for a loosely coupled multi-processor system and a device for realizing same
US5459837Apr 21, 1993Oct 17, 1995Digital Equipment CorporationSystem to facilitate efficient utilization of network resources in a computer network
US5559764Aug 18, 1994Sep 24, 1996International Business Machines CorporationHMC: A hybrid mirror-and-chained data replication method to support high data availability for disk arrays
US5740371Mar 18, 1996Apr 14, 1998International Business Machines CorporationLoad balancing of connections to parallel servers
US5774660Aug 5, 1996Jun 30, 1998Resonate, Inc.World-wide-web server with delayed resource-binding for resource-based load balancing on a distributed resource multi-node network
US5774668Jun 7, 1995Jun 30, 1998Microsoft CorporationSystem for on-line service in which gateway computer uses service map which includes loading condition of servers broadcasted by application servers for load balancing
US5828847Apr 19, 1996Oct 27, 1998Storage Technology CorporationDynamic server switching for maximum server availability and load balancing
US5864535Sep 18, 1996Jan 26, 1999International Business Machines CorporationIn a communications network
US5881238Feb 10, 1997Mar 9, 1999International Business Machines CorporationSystem for assignment of work requests by identifying servers in a multisystem complex having a minimum predefined capacity utilization at lowest importance level
US5890156May 2, 1996Mar 30, 1999Alcatel Usa, Inc.Distributed redundant database
US5894554Apr 23, 1996Apr 13, 1999Infospinner, Inc.System for managing dynamic web page generation requests by intercepting request at web server and routing to page server thereby releasing web server to process other requests
US5898870Dec 13, 1996Apr 27, 1999Hitachi, Ltd.Load balancing for a parallel computer system by employing resource utilization target values and states
US5915095Aug 8, 1995Jun 22, 1999Ncr CorporationMethod and apparatus for balancing processing requests among a plurality of servers based on measurable characteristics off network node and common application
US5933596Feb 19, 1997Aug 3, 1999International Business Machines CorporationMultiple server dynamic page link retargeting
US5933606Feb 19, 1997Aug 3, 1999International Business Machines CorporationSystem in a computer network
US5951694Feb 3, 1997Sep 14, 1999Microsoft CorporationMethod of redirecting a client service session to a second application server without interrupting the session by forwarding service-specific information to the second server
US5991808Jun 2, 1997Nov 23, 1999Digital Equipment CorporationTask processing optimization in a multiprocessor system
US6006259Nov 20, 1998Dec 21, 1999Network Alchemy, Inc.Method and apparatus for an internet protocol (IP) network clustering system
US6006264Mar 30, 1998Dec 21, 1999Arrowpoint Communications, Inc.Method and system for directing a flow between a client and a server
US6014660Dec 9, 1996Jan 11, 2000Sun Microsystems, Inc.Method and apparatus for client-sensitive name resolution using DNS
US6041307Jan 23, 1998Mar 21, 2000Lucent Technologies Inc.Technique for effectively managing resources in a network
US6070191 *Oct 17, 1997May 30, 2000Lucent Technologies Inc.Data distribution techniques for load-balanced fault-tolerant web access
US6076108 *Mar 6, 1998Jun 13, 2000I2 Technologies, Inc.System and method for maintaining a state for a user session using a web system having a global session server
US6098093 *Mar 19, 1998Aug 1, 2000International Business Machines Corp.Maintaining sessions in a clustered server environment
US6173322 *Jun 5, 1997Jan 9, 2001Silicon Graphics, Inc.Network request distribution based on static rules and dynamic performance data
US6263368 *Jun 19, 1997Jul 17, 2001Sun Microsystems, Inc.Network load balancing for multi-computer server by counting message packets to/from multi-computer server
US6405252 *Aug 23, 2000Jun 11, 2002Speedera Networks, Inc.Integrated point of presence server network
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US6760782 *Aug 4, 2000Jul 6, 2004Schneider Automation Inc.Apparatus for controlling internetwork communications
US6795859 *Mar 2, 2002Sep 21, 2004Dennis ParkerScalable server architecture systems and methods
US6850982 *Dec 19, 2000Feb 1, 2005Cisco Technology, Inc.Methods and apparatus for directing a flow of data between a client and multiple servers
US6865591 *Jun 30, 2000Mar 8, 2005Intel CorporationApparatus and method for building distributed fault-tolerant/high-availability computed applications
US6928481 *May 5, 2000Aug 9, 2005International Business Machines CorporationMethod, apparatus and program to optimize the network distribution of digital information based on hierarchical grouping of server topology and code distribution
US6954798 *Aug 28, 2002Oct 11, 2005Matsushita Electric Works, Ltd.Content-based routing of data from a provider to a requestor
US6970848 *Mar 23, 2001Nov 29, 2005Fujitsu LimitedMethod for authenticating users
US7003574 *Nov 1, 2000Feb 21, 2006Microsoft CorporationSession load balancing and use of VIP as source address for inter-cluster traffic through the use of a session identifier
US7043563 *Apr 16, 2001May 9, 2006Circadence CorporationMethod and system for redirection to arbitrary front-ends in a communication system
US7069325 *Dec 21, 2001Jun 27, 2006Cisco Technology, Inc.Method and apparatus for handling requests in a network
US7082465 *Mar 27, 2001Jul 25, 2006Cisco Technology, Inc.Web based management of host computers in an open protocol network
US7143168 *Jan 3, 2002Nov 28, 2006Cisco Technology, Inc.Resource sharing among multiple RSVP sessions
US7216212 *Mar 11, 2003May 8, 2007Stmicroelectronics, S.R.L.Semiconductor memory with self-refresh capability
US7246119 *Mar 7, 2003Jul 17, 2007Kabushiki Kaisha ToshibaMethod and implementation of session-based file locking for network applications
US7281043 *May 31, 2001Oct 9, 2007Cisco Technology, Inc.System for sharing resources among RSVP sessions
US7287090 *Jun 1, 2001Oct 23, 2007Noatak Software, LlcMethod and system for identifying a computing device in response to a request packet
US7305622 *Dec 5, 2001Dec 4, 2007Clickfox, LlcGraphical user interface and web site evaluation tool for customizing web sites
US7343396 *Jun 11, 2003Mar 11, 2008Fineground NetworksPrecomputation of web documents
US7346633Jun 10, 2004Mar 18, 2008Sybase, Inc.System providing methodology for replication subscription resolution
US7392421 *Mar 18, 2002Jun 24, 2008Symantec Operating CorporationFramework for managing clustering and replication
US7406538Aug 31, 2006Jul 29, 2008Noatak Software LlcMethod and system for identifying a computing device in response to an information packet
US7418522Jun 1, 2001Aug 26, 2008Noatak Software LlcMethod and system for communicating an information packet through multiple networks
US7421505Jun 1, 2001Sep 2, 2008Noatak Software LlcMethod and system for executing protocol stack instructions to form a packet for causing a computing device to perform an operation
US7454504 *Oct 23, 2006Nov 18, 2008Cisco Technology, Inc.Resource sharing among multiple RSVP sessions
US7483992 *Nov 30, 2005Jan 27, 2009Microsoft CorporationSession load balancing and use of VIP as source address for inter-cluster traffic through the use of a session identifier
US7487250 *Dec 20, 2004Feb 3, 2009Cisco Technology, Inc.Methods and apparatus for directing a flow of data between a client and multiple servers
US7487433 *Jun 10, 2005Feb 3, 2009Microsoft CorporationException handling in content based routing solutions
US7502823 *Feb 2, 2005Mar 10, 2009Intel CorporationApparatus and method for building distributed fault-tolerant/high-availability computer applications
US7506063Aug 31, 2006Mar 17, 2009Noatak Software LlcMethod and system for initiating execution of software in response to a state
US7512686Jun 1, 2001Mar 31, 2009Berg Mitchell TMethod and system for establishing a data structure of a connection with a client
US7512688 *Aug 16, 2002Mar 31, 2009Hitachi, Ltd.PPPoE network system that can distribute connection requests from PPPoE client terminals to specific PPPoE servers
US7516167 *Apr 22, 2005Apr 7, 2009Bea Systems, Inc.Data synchronization
US7543069 *Oct 18, 2004Jun 2, 2009International Business Machines CorporationDynamically updating session state affinity
US7546369Jun 1, 2001Jun 9, 2009Berg Mitchell TMethod and system for communicating a request packet in response to a state
US7613822 *Jun 30, 2003Nov 3, 2009Microsoft CorporationNetwork load balancing with session information
US7640298Nov 1, 2005Dec 29, 2009Berg Mitchell TMethod and system for communicating an information packet through multiple router devices
US7649876Aug 31, 2006Jan 19, 2010Berg Mitchell TMethod and system for communicating an information packet through multiple router devices
US7656885 *May 25, 2004Feb 2, 2010Sybase 365, Inc.Intermediary content gateway system and method
US7693995 *Feb 28, 2006Apr 6, 2010Hitachi, Ltd.Arbitration apparatus for allocating computer resource and arbitration method therefor
US7769823 *Sep 28, 2001Aug 3, 2010F5 Networks, Inc.Method and system for distributing requests for content
US7783763Jun 6, 2006Aug 24, 2010International Business Machines CorporationManaging stateful data in a partitioned application server environment
US7809935 *Aug 11, 2006Oct 5, 2010Hitachi, Ltd.Computer system for selecting a useable computer board to power on and accessing corresponding storage based on terminal request that includes user information
US7827237Mar 12, 2007Nov 2, 2010Citrix Systems, Inc.Systems and methods for identifying long matches of data in a compression history
US7865585 *Mar 12, 2007Jan 4, 2011Citrix Systems, Inc.Systems and methods for providing dynamic ad hoc proxy-cache hierarchies
US7872597Oct 5, 2009Jan 18, 2011Citrix Systems, Inc.Systems and methods of using application and protocol specific parsing for compression
US7895356 *Dec 31, 2003Feb 22, 2011Nec Infrontia CorporationIP router, communication system and band setting method used therein and its program
US7916047Oct 16, 2008Mar 29, 2011Citrix Systems, Inc.Systems and methods of clustered sharing of compression histories
US7953087 *Dec 28, 2001May 31, 2011The Directv Group, Inc.Content filtering using static source routes
US7962603 *Jun 6, 2000Jun 14, 2011Nobuyoshi MorimotoSystem and method for identifying individual users accessing a web site
US8051127May 26, 2010Nov 1, 2011Citrix Systems, Inc.Systems and methods for identifying long matches of data in a compression history
US8063799Mar 30, 2009Nov 22, 2011Citrix Systems, Inc.Systems and methods for sharing compression histories between multiple devices
US8095654Jun 13, 2011Jan 10, 2012Nobuyoshi MorimotoSystem and method for identifying individual users accessing a web site
US8103746Jun 21, 2010Jan 24, 2012F5 Networks, Inc.Method and system for distributing requests for content
US8140659 *May 8, 2001Mar 20, 2012Hewlett-Packard Development Company, L.P.Calculating an estimated time to complete a request
US8255570Mar 12, 2007Aug 28, 2012Citrix Systems, Inc.Systems and methods of compression history expiration and synchronization
US8271678 *Apr 3, 2001Sep 18, 2012Arbor Networks, Inc.Independent detection and filtering of undesirable packets
US8341288 *Oct 22, 2004Dec 25, 2012Cisco Technology, Inc.Mechanism for sharing resources among different senders and receivers
US8341290Aug 31, 2006Dec 25, 2012Noatak Software LlcMethod and system for selecting a computing device for maintaining a client session in response to a request packet
US8352597Dec 30, 2011Jan 8, 2013F5 Networks, Inc.Method and system for distributing requests for content
US8352605Dec 29, 2010Jan 8, 2013Citrix Systems, Inc.Systems and methods for providing dynamic ad hoc proxy-cache hierarchies
US8352634 *Apr 6, 2007Jan 8, 2013International Business Machines CorporationOn-demand propagation of routing information in distributed computing system
US8386575 *Mar 12, 2010Feb 26, 2013Fujitsu LimitedMethod of realizing uniqueness assurance and method of determining message destination
US8522147Sep 20, 2011Aug 27, 2013Go Daddy Operating Company, LLCMethods for verifying person's identity through person's social circle using person's photograph
US8538065Sep 20, 2011Sep 17, 2013Go Daddy Operating Company, LLCSystems for verifying person's identity through person's social circle using person's photograph
US8613039 *Jun 3, 2008Dec 17, 2013International Business Machines CorporationAutomated correction and reporting for dynamic web applications
US8699349 *Oct 26, 2007Apr 15, 2014Microsoft CorporationMulti-factor optimized routing
US8706816Jun 24, 2005Apr 22, 2014Go Daddy Operating Company, LLCSystem and method for email delivery for shared domain name
US8738604Mar 30, 2012May 27, 2014Go Daddy Operating Company, LLCMethods for discovering sensitive information on computer networks
US8738605Mar 30, 2012May 27, 2014Go Daddy Operating Company, LLCSystems for discovering sensitive information on computer networks
US20060089988 *Oct 22, 2004Apr 27, 2006Davie Bruce SMechanism for sharing resources among different senders and receivers
US20080250099 *Apr 6, 2007Oct 9, 2008Jinmei ShenOn-Demand Propagation of Routing Information in Distributed Computing System
US20090024748 *Jan 29, 2007Jan 22, 2009Speed-Trap, Com LinitedWebsite monitoring and cookie setting
US20090300709 *Jun 3, 2008Dec 3, 2009International Business Machines CorporationAutomated correction and reporting for dynamic web applications
US20100241715 *Mar 12, 2010Sep 23, 2010Fujitsu LimitedMethod of realizing uniqueness assurance and method of determining message destination
US20110282909 *Jul 27, 2011Nov 17, 2011Intuit Inc.Secregating anonymous access to dynamic content on a web server, with cached logons
US20130086020 *Sep 30, 2011Apr 4, 2013Apple Inc.Interactive Web Application Framework
US20130086102 *Sep 30, 2011Apr 4, 2013Apple Inc.Asynchronous Communication in Web Applications
US20130086146 *Sep 30, 2011Apr 4, 2013Apple Inc.Notification Based Web Applications
WO2004021250A1 *Aug 27, 2003Mar 11, 2004Emware IncContent-based routing of data from a provider to a requestor
Classifications
U.S. Classification709/219, 709/226, 709/229, 709/228
International ClassificationG06F, G06F13/00, G06F15/173, G06F7/00, G06F9/00, G06F15/16
Cooperative ClassificationH04L67/142, H04L67/02, H04L67/141, H04L67/327, H04L67/1008, H04L67/146
European ClassificationH04L29/08N13J, H04L29/08N13B, H04L29/08N31Y, H04L29/08N9A1B, H04L29/08N13A, H04L29/08N1
Legal Events
DateCodeEventDescription
Sep 11, 2007FPExpired due to failure to pay maintenance fee
Effective date: 20070722
Jul 22, 2007LAPSLapse for failure to pay maintenance fees
Feb 7, 2007REMIMaintenance fee reminder mailed
May 18, 2001ASAssignment
Owner name: WARP SOLUTIONS, INC., NEW YORK
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PRIMAK, LEONARD;CHEN, KAILAI;GNIP, JOHN;REEL/FRAME:011825/0839;SIGNING DATES FROM 20001207 TO 20001211
Owner name: WARP SOLUTIONS, INC. 627 GREENWICH STREET, 12TH FL
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PRIMAK, LEONARD /AR;REEL/FRAME:011825/0839;SIGNING DATESFROM 20001207 TO 20001211