US20030158951A1 - System and method for dynamic content routing - Google Patents
System and method for dynamic content routing Download PDFInfo
- Publication number
- US20030158951A1 US20030158951A1 US10/384,284 US38428403A US2003158951A1 US 20030158951 A1 US20030158951 A1 US 20030158951A1 US 38428403 A US38428403 A US 38428403A US 2003158951 A1 US2003158951 A1 US 2003158951A1
- Authority
- US
- United States
- Prior art keywords
- content
- session
- server
- client
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/142—Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Definitions
- 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.
- the web server layer typically has one or more web server clusters, each web server cluster having a plurality of web servers.
- 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.
- 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.
- 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.
- TCP/IP standard communication protocols
- 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.
- the web site owner 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.
- both of these options are costly and complicated propositions for web site owners and/or operators.
- 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.
- the present invention provides a system and method for identifying the dynamic content involved in every client request requiring access to the dynamic content.
- 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.
- 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 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.
- 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.
- 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.
- 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.
- the system additionally includes an application server proxy that acts as an interface between the web servers and application servers utilizing proprietary communications protocols.
- 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.
- 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.
- 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.
- 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.
- 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 .
- 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.
- 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.
- the dynamic content of the client can be represented by a content label.
- 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.
- 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.
- 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.
- the mirrored content can be active at the same time while maintaining its transactional integrity.
- 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”.
- the segmentable content can represent cash balances, transactions, account holdings, personal information, etc.
- non-segmentable content can represent data shared by all account, such as margin rate, stock quotes, bond prices, and the like. content.
- 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.
- 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.
- 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.
- 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.
- the present invention provides a system and method for identifying the dynamic content involved in every client request requiring access to the dynamic content.
- 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 .
- 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.
- the client request can be identified by its content label before the request is routed to the appropriate database 40 a or 40 b.
- 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 .
- the dynamic content router saves the session ID in the session table 12 (FIG. 4).
- 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).
- the dynamic content router 10 (FIG.
- 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.
- 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.
- 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 .
- the receiving web server 20 provides the client 60 with the requested stagnant 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 .
- 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 .
- 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 .
- 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 .
- the application server 30 c is connected to the database 40 a and is part of the application server cluster 130 .
- 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.
- 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 .
- the replication agents 42 can reside in a separate host or server to monitor any number of databases.
- 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 .
- 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.
- 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.
- 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 .
- 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.
- 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 .
- each record in the session table 12 has at least three fields: a session ID, a content ID and a session server ID.
- the application server 30 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 .
- the session ID can be a cookie or some other unique code for identifying the client 60 by the application server 30 .
- all subsequent requests from the client 60 generally include the session ID.
- 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.
- the dynamic content router 10 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.
- 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 .
- the user associated with the client 60 can provide his/her identity through a login or signing in process, e.g., entering a name and password onto a login screen.
- 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.
- 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 .
- 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 .
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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 .
- 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.
- 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 .
- 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 .
- 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 .
- the application server 30 a establishes a session with the client 60 and sends back a session ID to 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 .
- 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.
- 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.
- 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 .
- 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 .
- 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.
- a content record containing the unique content ID of the client exists in each content table 14 of the dynamic content routers 10 .
- the plug-in 22 of the web server 20 extracts the content ID corresponding to a content label from the login request.
- the content label can be a field name assigned by an application.
- the content label can represent an account number for a trading application and a login id for an e-commerce site application.
- the content label has an associated value that is assigned during the login process.
- 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.
- 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.
- 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.
- the content can be updated on database server 40 a or 40 b directly (bypassing the web servers 20 and the application servers 30 ).
- 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.
- a utility process (not shown) is used directly update the database 40 and to communicate with the dynamic content router 10 .
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.
Description
- This application is a continuation-in-part of U.S. provisional patent application Serial No. 60/241,528, filed Oct. 17, 2000; a continuation-in-part of patent application Ser. No. 09/565,259, filed May 5, 2000, which is a continuation-in-part of U.S. provisional patent application Serial No. 60/169,196, filed Dec. 6, 1999; a continuation-in-part of U.S. provisional patent application Serial 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.
- 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.
- 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 pending U.S. patent application No. 09/565,259 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 not 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.
- 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.
- 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.
- 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 adynamic content router 10 in accordance with an embodiment of the present invention. Theweb site 100 has two overlappingweb server clusters 110 and 120. Theweb server cluster 110 comprisesweb servers 20 a to 20 e and the second web server cluster comprisingweb servers 20 d to 20 g. Additionally, there are twoapplication server clusters application server cluster 130 comprisesapplication servers 30 a to 30 c and theapplication server cluster 140 comprisesservers 30 d to 30 g. Theapplication server clusters database databases - 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 - 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 theweb 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 theappropriate database - After a
client 60 accesses one of theapplication servers 30 a to 30 g for the first time, that application server assigns and maintains a session ID for theclient 60. Thereafter, every client request from theclient 60 includes the session ID and the application server uses the session ID to identify theclient 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 thedynamic 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, thedynamic router 10 can extract the session ID from the client request. The extracted session ID then can be used by thedynamic 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, thedynamic 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, thedynamic 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, thedynamic 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 thedynamic 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 theweb servers 20 a to 20 g, referred to hereinafter as the receiving web server 20. When theclient 60 requests stagnant content, the receiving web server 20 provides theclient 60 with the requested stagnant content. However, if theclient 60 requests dynamic content, a plug-in 22 (FIG. 2), which is integrated into each web server, routes or directs the request from theclient 60 to thedynamic content router 10. Thedynamic content router 10 evaluates the request and selects an application server 30 based on its evaluation of the request. Also, thedynamic content router 10 sends an instruction to the plug-in 22 of the web server 30 to direct all request from theclient 60 to the selected application server 30. - Turning now to FIG. 2, there is illustrated an example of the plug-in22 of the web server 30 transmitting the request for dynamic content from the
client 60 to thedynamic content router 10 and then to an application server 30 selected by thedynamic content router 10. Based on its review or evaluation of the request, thedynamic content router 10 selects an appropriate application server 30 that is best suited to provide the requested content or data to theclient 60. For example, in FIG. 2, thedynamic content router 10 selects theapplication server 30 c based on its evaluation of the request, and informs the plug-in 22 b of theweb server 20 b to direct or route all requests from theclient 60 to theapplication server 30 c. As shown in FIG. 2, theapplication server 30 c is connected to thedatabase 40 a and is part of theapplication server cluster 130. - Turning now to FIG. 3, there is illustrated an embodiment of the application server32 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. Thedynamic 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 replication agents databases dynamic content router 10. Preferably, thedynamic 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 thedynamic content router 10. This enables thedynamic content router 10 to isolate the disabled or failed database. For example, if thedatabase 40 a is disabled, then thedynamic content router 10 can instruct the plug-ins 22 to route all requests for content to theapplication server cluster 140 which is connected to thedatabase 40 b. That is, the requests are no longer routed to theapplication server cluster 130 that is connected to thedisabled database 40 a. - In accordance with an embodiment of the present invention, each replication agent42 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 thedynamic content router 10. - Preferably, the replication agents42 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 aclient 60, the application server 30 generates and transmits a session identifier (or a session ID) to theclient 60. For example, the session ID can be a cookie or some other unique code for identifying theclient 60 by the application server 30. During the session, all subsequent requests from theclient 60 generally include the session ID. - Using FIG. 2 as an example, when a request is received by the
web server 20 b from theclient 60, the plug-in 22 b of theweb server 20 b transmits the request to thedynamic content router 10. Thedynamic 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 theapplication server 30 c that established the current session with theclient 60 and issued the session ID. - Each time a request for content is received from the
client 60, thedynamic content router 10 examines the header of the request for a session ID. If the request contains a session ID, thedynamic 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, thedynamic 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, thedynamic 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. Thedynamic 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 theclient 60. For example, thedynamic 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, thedynamic 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 torouter 10 by plug-in 22. Therouter 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-in22 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 theclient 60 to thedynamic content router 10. Thedynamic content router 10 compares the content ID of theclient 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, thedynamic content router 10 generates a new content record for theclient 60 in the content table 14. The new content record contains at least the content ID of theclient 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 theclient 60. Accordingly, on each subsequent visit to the web site by theclient 60, thedynamic content router 10 locates the content record of theclient 60 from the content table 14. The content record of theclient 60 includes the time and date of the client's last login or session and the identification of the application server 30 accessed by theclient 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, thedynamic 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. Thedynamic 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 twodatabases 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 thedynamic 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 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 theclient 60. That is, thedynamic 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, thedynamic 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. Thedynamic content router 10 sends the set session response to the plug-in 22, which forwards it to theclient 60. Thereafter, theclient 60 includes the new session ID in its requests. Once the plug-in 22 facilitates the establishment of a new session between theclient 60 and the new session server 30 (the last accessed application server), thedynamic 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. Thedynamic 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 theclient 60. - The database replication latency table16 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 multipledynamic content routers 10 andapplication server proxies 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 theweb server 20e, then the plug-in 22 e of theweb server 20 e transmits the request to one of thedynamic content routers 10 a to 10 c. Preferably, the plug-in 22 e selects thedynamic content router 10 based on load information transmitted byload agents 150 a to 150 c residing and running on thedynamic content routers 10 a to 10 c, respectively. That is, the plug-in 22 e selects thedynamic content router 10 with the lowest load. For example, the plug-in 22 can select thedynamic content router 10 c as having the lowest load. It is appreciated that the tables 12, 14, 16 and 18 residing in each of thedynamic content routers 10 a to 10 c are continuously replicated, thereby maintaining the mirrored state of thedynamic content routers 10 a to 10 c. - The selected
dynamic content router 10 c examines the request from theclient 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 selecteddynamic 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, thedynamic content router 10 c can select theapplication server 30 a belonging to theapplication server cluster 130 as having the lower load value. In such case, thedynamic content router 10 c instructs the plug-in 22 e to route the client's request to theapplication server cluster 130 via theapplication server proxy 50 a. The plug-in 22 e sends the client's request to theapplication proxy 50 a using standard TCP/IP protocols. The proxy 50 a converts the request to conform to the proprietary protocol utilized by theapplication servers 30 a to 30 c belonging to theapplication cluster 130 and forwards the request to the selectedapplication server 30 a. In response to the request, theapplication server 30 a establishes a session with theclient 60 and sends back a session ID to theclient 60. Before the session ID reaches theclient 60, the plug-in 22 e intercepts the session ID and sends a copy of the session ID to thedynamic router 10 c. Thedynamic 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 theweb server 20 e. For example, if theweb server 20 b receives the second request bearing the session ID issued by theapplication server 30 a from the client, the plug-in 22 b sends the request to thedynamic content router 10 a (currently the least loaded dynamic content router). Since all of thedynamic content routers 10 are mirrored, the session record previously generated by thedynamic content router 10 c is available from any dynamic content router's session table. That is, the session table residing in thedynamic content router 10 a contains all of the session records generated by thedynamic content routers 10 a to 10 c. Thedynamic 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, thedynamic 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 theapplication 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, thedynamic content router 10 a checks its content table 14 to determine if theclient 60 is a return visitor or a first time visitor. If it is determined that theclient 60 is a return visitor (i.e., a matching content record exists), then thedynamic content router 10 a obtains the last accessed server information from the matching content record. However, if it is determined that theclient 60 is a first time visitor (i.e., no matching content record exists), then thedynamic content router 10 a inserts a new content record for theclient 60 into the content table 14. It is appreciated that thedynamic content router 10 a does not direct the plug-in 22 b to make any change with respect to the client's session with theapplication server 30 a since thisnew client 60 is not being transferred to any last accessed application server. - In accordance with an embodiment of the present invention, the application server30 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 thedatabase 40 b. It is appreciated that the activity data of theclient 60 may not have been replicated to all of the databases 40 by the time theclient 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 thedynamic 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, thedynamic 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, thedynamic 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 theapplication server 30 f and the last accessed server is theapplication server 30 a (i.e., there is a mismatch of session servers), thedynamic 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, thedynamic 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, thedynamic content router 10 directs the plug-in 22 which sent the content ID to thedynamic content router 10 to facilitate a new session between theclient 60 and the last accessed server. Once the new session is established, thedynamic 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 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 thedynamic 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.
Claims (26)
1. A method of dynamic content routing a client request to an application server, comprising the steps of:
receiving said request for content from a client over a communications network;
determining a dynamic content associated with said request;
selecting an application server from a plurality of application servers in accordance with said dynamic content; and
routing said request to said selected application server.
2. The method of claim 1 , further comprising the step of transmitting said requested content from said selected application server to said client.
3. The method of claim 1 , wherein the step of selecting includes the step of selecting an application server connected to a database having data relevant to said requested content.
4. The method of claim 3 , wherein the step of selecting includes the step of selecting an application server based on an available processing capacity of said database.
5. The method of claim 1 , further comprising the steps of
determining if a session exists between said client and one of said plurality of application servers;
establishing a session between said client and said selected application server if it is determined that a session does not exists between said client and one of said plurality of application servers to provide a session ID and a session time;
associating said dynamic content with said session ID to provide a link;
storing said link, said session ID and said session time as a last session time; and
transmitting said request for content to said selected application server by said client, said request having at least said session ID.
6. The method of claim 5 , wherein the step of selecting includes the step of selecting an application server based on session persistence.
7. The method of claim 5 , wherein the step of determining includes the steps of:
reading said session ID from said request to determine said link; and
determining said dynamic content as a function of said link.
8. The method of claim 1 , further comprising the step of storing said selected server as a last accessed server.
9. The method of claim 8 , wherein said plurality of application servers are grouped into one or more server clusters, each server cluster being associated with a database.
10. The method of claim 9 , further comprising the step of determining replication latencies between said databases; and storing said replication latencies.
11. The method of claim 10 , wherein the step of selecting includes the step of selecting an application server as a function of said replication latencies.
12. The method of claim 10 , 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 said selected server is different from the database connected to said last accessed server for said client to provide a session interval; and
selecting said last accessed server as said selected server if said replication latency between the databases connected to said last accessed server and said selected server exceeds said session interval.
13. A method of mirroring content in a database, comprising the steps of:
categorizing each content into either segmentable or non-segmentable content;
dividing said segmentable content into one or more segments;
labeling each segment of said segmentable content with a content label;
storing said non-segmentable content and each segment of said segmentable content, thereby effectively mirroring said content.
14. The method of claim 13 , further comprising the steps of receiving a request for content stored in said database; categorizing said request by content label and searching said database for said requested content in accordance with said content label.
15. A system for dynamic content routing a client request to an application server, comprising:
a web server for receiving said request for content from a client over a communications network;
a dynamic content router for determining a dynamic content associated with said request and selecting an application server from a plurality of application servers connected to said network in accordance with said dynamic content; and
wherein said web server is operable to route said request to said selected application server.
16. The system of claim 15 , further comprising one or more databases connected to said plurality of application servers, each database having a plurality of data; and wherein said selected application server is operable to transmit said requested content from an associated database to said client.
17. The system of claim 15 , wherein said router is operable to select an application server connected to a database having data relevant to said requested content.
18. The system of claim 17 , wherein said router is operable to select an application server based on an available processing capacity of said database.
19. The system of claim 15 , wherein said router is operable to determine if a session exists between said client and one of said plurality of application servers, establish a session between said client and said selected application server if it is determined that a session does not exists between said client and one of said plurality of application servers to provide a session ID and a session time, associate said dynamic content with said session ID to provide a link, store said link, said session ID and said session time as a last session time, and transmit said request for content to said selected application server by said client, said request having at least said session ID.
20. The system of claim 19 , wherein said router is operable to select an application server based on session persistence.
21. The system of claim 19 , wherein said router is operable to read said session ID from said request to determine said link and determine said dynamic content as a function of said link.
22. The system of claim 15 , wherein said router is operable to store said selected server as a last accessed server.
23. The system of claim 22 , wherein said plurality of application servers are grouped into one or more server clusters, each server cluster being associated with a database.
24. The system of claim 23 , 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.
25. The system of claim 24 , wherein said router is operable to select an application server as a function of said replication latencies.
26. The system of claim 24 , 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 is different from the database connected to said last accessed server for said client to provide a session interval; and
selecting said last accessed server as said selected server if said replication latency between the databases connected to said last accessed server and said selected server exceeds said session interval.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/384,284 US20030158951A1 (en) | 1999-12-06 | 2003-03-07 | System and method for dynamic content routing |
Applications Claiming Priority (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16919699P | 1999-12-06 | 1999-12-06 | |
US20180100P | 2000-05-04 | 2000-05-04 | |
US20232900P | 2000-05-05 | 2000-05-05 | |
US09/565,259 US6389448B1 (en) | 1999-12-06 | 2000-05-05 | System and method for load balancing |
US24152800P | 2000-10-17 | 2000-10-17 | |
US09/730,130 US6586954B2 (en) | 1998-02-10 | 2000-12-04 | Probe tile for probing semiconductor wafer |
US10/384,284 US20030158951A1 (en) | 1999-12-06 | 2003-03-07 | System and method for dynamic content routing |
Related Parent Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/565,259 Continuation US6389448B1 (en) | 1999-12-06 | 2000-05-05 | System and method for load balancing |
US09/730,130 Continuation US6586954B2 (en) | 1997-04-08 | 2000-12-04 | Probe tile for probing semiconductor wafer |
Publications (1)
Publication Number | Publication Date |
---|---|
US20030158951A1 true US20030158951A1 (en) | 2003-08-21 |
Family
ID=27538793
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/730,259 Expired - Fee Related US6598077B2 (en) | 1999-12-06 | 2000-12-05 | System and method for dynamic content routing |
US10/384,284 Abandoned US20030158951A1 (en) | 1999-12-06 | 2003-03-07 | System and method for dynamic content routing |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/730,259 Expired - Fee Related US6598077B2 (en) | 1999-12-06 | 2000-12-05 | System and method for dynamic content routing |
Country Status (3)
Country | Link |
---|---|
US (2) | US6598077B2 (en) |
AU (1) | AU4717901A (en) |
WO (1) | WO2001044894A2 (en) |
Cited By (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030028669A1 (en) * | 2001-07-06 | 2003-02-06 | Alcatel | Method and system for routing logging a request |
US20030120722A1 (en) * | 2001-12-20 | 2003-06-26 | Forkner Damien R. | Persistent process software architecture |
US20050025051A1 (en) * | 2003-08-01 | 2005-02-03 | Roeder Michael T. | Automated router load balancing |
US20050038772A1 (en) * | 2003-08-14 | 2005-02-17 | Oracle International Corporation | Fast application notification in a clustered computing system |
US20050038833A1 (en) * | 2003-08-14 | 2005-02-17 | Oracle International Corporation | Managing workload by service |
US20050080885A1 (en) * | 2003-09-26 | 2005-04-14 | Imran Ahmed | Autonomic monitoring for web high availability |
US20050185596A1 (en) * | 2000-11-28 | 2005-08-25 | Navic Systems, Inc. | Load balancing in set top cable box environment |
US20060089965A1 (en) * | 2004-10-26 | 2006-04-27 | International Business Machines Corporation | Dynamic linkage of an application server and a Web server |
US20070005613A1 (en) * | 2005-06-29 | 2007-01-04 | Visa U.S.A., Inc. | Schema-based dynamic parse/build engine for parsing multi-format messages |
US20070005774A1 (en) * | 2005-06-29 | 2007-01-04 | Visa U.S.A., Inc. | Adaptive gateway for switching transactions and data on unreliable networks using context-based rules |
US20080022386A1 (en) * | 2006-06-08 | 2008-01-24 | Shevchenko Oleksiy Yu | Security mechanism for server protection |
US20080091806A1 (en) * | 2006-10-11 | 2008-04-17 | Jinmei Shen | Dynamic On-Demand Clustering |
US20080250099A1 (en) * | 2007-04-06 | 2008-10-09 | Jinmei Shen | On-Demand Propagation of Routing Information in Distributed Computing System |
US20100257539A1 (en) * | 2009-03-31 | 2010-10-07 | Krishnakumar Narayanan | System, method and apparatus for providing functions to applications on a digital electronic device |
US7840588B2 (en) | 2004-03-25 | 2010-11-23 | International Business Machines Corporation | Real-time attribute processor and syntax schema for directory access protocol services |
US7853579B2 (en) | 2003-08-14 | 2010-12-14 | Oracle International Corporation | Methods, systems and software for identifying and managing database work |
US20110179181A1 (en) * | 2008-06-03 | 2011-07-21 | Ian Gordan Elz | Identifying User Role in IP Multimedia Subsystem |
US8543508B2 (en) | 2010-07-09 | 2013-09-24 | Visa International Service Association | Gateway abstraction layer |
US8713186B2 (en) | 2007-03-13 | 2014-04-29 | Oracle International Corporation | Server-side connection resource pooling |
US20150134845A1 (en) * | 2000-05-31 | 2015-05-14 | Ganas Llc | Object Oriented Communication Among Platform Independent Systems over Networks Using SOAP |
US9229999B2 (en) | 2013-03-15 | 2016-01-05 | International Business Machines Corporation | Using average replication latency to influence routing query transactions |
US9298455B1 (en) * | 2013-03-15 | 2016-03-29 | Instart Logic, Inc. | Provisional execution of dynamic content component |
US9363329B1 (en) * | 2013-03-15 | 2016-06-07 | Instart Logic, Inc. | Identifying correlated components of dynamic content |
US9813480B2 (en) | 2015-01-08 | 2017-11-07 | Instart Logic, Inc. | Placeholders for dynamic components in HTML streaming |
US10474653B2 (en) | 2016-09-30 | 2019-11-12 | Oracle International Corporation | Flexible in-memory column store placement |
Families Citing this family (145)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6795859B2 (en) * | 2000-01-21 | 2004-09-21 | Dennis Parker | Scalable server architecture systems and methods |
US6757291B1 (en) | 2000-02-10 | 2004-06-29 | Simpletech, Inc. | System for bypassing a server to achieve higher throughput between data network and data storage system |
CA2404095A1 (en) * | 2000-03-22 | 2001-09-27 | Yottayotta, Inc. | Method and system for providing multimedia information on demand over wide area networks |
WO2001080024A2 (en) * | 2000-04-17 | 2001-10-25 | Circadence Corporation | Gateway buffer prioritization |
US6928481B1 (en) * | 2000-05-05 | 2005-08-09 | International Business Machines Corporation | Method, apparatus and program to optimize the network distribution of digital information based on hierarchical grouping of server topology and code distribution |
US7962603B1 (en) | 2000-06-06 | 2011-06-14 | Nobuyoshi Morimoto | System and method for identifying individual users accessing a web site |
US6865591B1 (en) * | 2000-06-30 | 2005-03-08 | Intel Corporation | Apparatus and method for building distributed fault-tolerant/high-availability computed applications |
US8566248B1 (en) * | 2000-08-04 | 2013-10-22 | Grdn. Net Solutions, Llc | Initiation of an information transaction over a network via a wireless device |
US6760782B1 (en) * | 2000-08-04 | 2004-07-06 | Schneider Automation Inc. | Apparatus for controlling internetwork communications |
US7263550B1 (en) | 2000-10-10 | 2007-08-28 | Juniper Networks, Inc. | Agent-based event-driven web server architecture |
JP4838414B2 (en) * | 2000-10-11 | 2011-12-14 | 富士通株式会社 | Authentication method |
US7606898B1 (en) | 2000-10-24 | 2009-10-20 | Microsoft Corporation | System and method for distributed management of shared computers |
US7003574B1 (en) * | 2000-11-01 | 2006-02-21 | Microsoft Corporation | Session load balancing and use of VIP as source address for inter-cluster traffic through the use of a session identifier |
WO2002045316A2 (en) * | 2000-11-10 | 2002-06-06 | Full Audio Corporation | Digital content distribution and subscription system |
AU2002220126A1 (en) * | 2000-12-05 | 2002-06-18 | Clickfox, Llc | Graphical user interface and evaluation tool for customizing web sites |
US6697206B2 (en) * | 2000-12-19 | 2004-02-24 | Imation Corp. | Tape edge monitoring |
US6850982B1 (en) * | 2000-12-19 | 2005-02-01 | Cisco Technology, Inc. | Methods and apparatus for directing a flow of data between a client and multiple servers |
US20020116397A1 (en) * | 2000-12-21 | 2002-08-22 | Berg Mitchell T. | Method and system for communicating an information packet through multiple router devices |
US20020116605A1 (en) * | 2000-12-21 | 2002-08-22 | Berg Mitchell T. | Method and system for initiating execution of software in response to a state |
US7421505B2 (en) * | 2000-12-21 | 2008-09-02 | Noatak Software Llc | Method and system for executing protocol stack instructions to form a packet for causing a computing device to perform an operation |
US7418522B2 (en) * | 2000-12-21 | 2008-08-26 | Noatak Software Llc | Method and system for communicating an information packet through multiple networks |
US7512686B2 (en) | 2000-12-21 | 2009-03-31 | Berg Mitchell T | Method and system for establishing a data structure of a connection with a client |
US20020116532A1 (en) * | 2000-12-21 | 2002-08-22 | Berg Mitchell T. | Method and system for communicating an information packet and identifying a data structure |
US7546369B2 (en) * | 2000-12-21 | 2009-06-09 | Berg Mitchell T | Method and system for communicating a request packet in response to a state |
US7287090B1 (en) * | 2000-12-21 | 2007-10-23 | Noatak Software, Llc | Method and system for identifying a computing device in response to a request packet |
US20020107939A1 (en) * | 2001-02-07 | 2002-08-08 | Ford Daniel E. | System and method for accessing software components in a distributed network environment |
US20020120751A1 (en) * | 2001-02-23 | 2002-08-29 | Chris Del Sordo | Control channel protocol and hardware-independent downstream services software design for broadband devices |
US7082465B1 (en) * | 2001-03-27 | 2006-07-25 | Cisco Technology, Inc. | Web based management of host computers in an open protocol network |
US8271678B2 (en) * | 2001-04-03 | 2012-09-18 | Arbor Networks, Inc. | Independent detection and filtering of undesirable packets |
TWI220821B (en) * | 2001-04-26 | 2004-09-01 | Accton Technology Corp | Zero-loss web service system and method |
US7543066B2 (en) * | 2001-04-30 | 2009-06-02 | International Business Machines Corporation | Method and apparatus for maintaining session affinity across multiple server groups |
US8140659B2 (en) * | 2001-05-08 | 2012-03-20 | Hewlett-Packard Development Company, L.P. | Calculating an estimated time to complete a request |
US7212527B2 (en) * | 2001-05-09 | 2007-05-01 | Intel Corporation | Method and apparatus for communicating using labeled data packets in a network |
US7281043B1 (en) * | 2001-05-31 | 2007-10-09 | Cisco Technology, Inc. | System for sharing resources among RSVP sessions |
US7320131B1 (en) * | 2001-06-06 | 2008-01-15 | Cisco Technology, Inc. | Methods and apparatus for selecting a server to process a request |
CN100568214C (en) | 2001-07-16 | 2009-12-09 | Bea系统公司 | The method and apparatus that is used for session replication and failover |
WO2003017123A1 (en) * | 2001-08-16 | 2003-02-27 | Redline Networks, Inc. | System and method for maintaining statefulness during client-server interactions |
US7769823B2 (en) * | 2001-09-28 | 2010-08-03 | F5 Networks, Inc. | Method and system for distributing requests for content |
US7367014B2 (en) * | 2001-10-24 | 2008-04-29 | Bea Systems, Inc. | System and method for XML data representation of portlets |
US7069325B1 (en) * | 2001-12-21 | 2006-06-27 | Cisco Technology, Inc. | Method and apparatus for handling requests in a network |
US7953087B1 (en) * | 2001-12-28 | 2011-05-31 | The Directv Group, Inc. | Content filtering using static source routes |
JP4080765B2 (en) * | 2002-03-01 | 2008-04-23 | 株式会社日立製作所 | Network system |
US7246119B2 (en) * | 2002-03-08 | 2007-07-17 | Kabushiki Kaisha Toshiba | Method and implementation of session-based file locking for network applications |
EP1345234A1 (en) * | 2002-03-11 | 2003-09-17 | STMicroelectronics S.r.l. | Semiconductor memory with self-refresh capability |
US7392421B1 (en) * | 2002-03-18 | 2008-06-24 | Symantec Operating Corporation | Framework for managing clustering and replication |
US7146400B2 (en) * | 2002-05-29 | 2006-12-05 | International Business Machines Corporation | Web and lotus notes adapter layers |
US7343396B2 (en) * | 2002-06-20 | 2008-03-11 | Fineground Networks | Precomputation of web documents |
US20040216122A1 (en) * | 2002-07-23 | 2004-10-28 | Charles Gram | Method for routing data through multiple applications |
WO2004012412A2 (en) * | 2002-07-25 | 2004-02-05 | Yee James D | System and method for providing computer services |
US6954798B2 (en) * | 2002-08-28 | 2005-10-11 | Matsushita Electric Works, Ltd. | Content-based routing of data from a provider to a requestor |
US7296076B1 (en) * | 2002-10-23 | 2007-11-13 | Cisco Technology, Inc. | Maintaining session persistence without client-supported cookies |
JP4108486B2 (en) * | 2003-01-08 | 2008-06-25 | Necインフロンティア株式会社 | IP router, communication system, bandwidth setting method used therefor, and program thereof |
US8831966B2 (en) | 2003-02-14 | 2014-09-09 | Oracle International Corporation | Method for delegated administration |
US7653930B2 (en) | 2003-02-14 | 2010-01-26 | Bea Systems, Inc. | Method for role and resource policy management optimization |
US7591000B2 (en) | 2003-02-14 | 2009-09-15 | Oracle International Corporation | System and method for hierarchical role-based entitlements |
US7890543B2 (en) | 2003-03-06 | 2011-02-15 | Microsoft Corporation | Architecture for distributed computing system and automated design, deployment, and management of distributed applications |
US7689676B2 (en) | 2003-03-06 | 2010-03-30 | Microsoft Corporation | Model-based policy application |
US8122106B2 (en) | 2003-03-06 | 2012-02-21 | Microsoft Corporation | Integrating design, deployment, and management phases for systems |
US20050169254A1 (en) * | 2003-04-14 | 2005-08-04 | Fujitsu Limited | Data relay apparatus, data relay method, data relay program, service selection apparatus, service selection method and service selection program |
US7567504B2 (en) * | 2003-06-30 | 2009-07-28 | Microsoft Corporation | Network load balancing with traffic routing |
US7636917B2 (en) * | 2003-06-30 | 2009-12-22 | Microsoft Corporation | Network load balancing with host status information |
US7606929B2 (en) * | 2003-06-30 | 2009-10-20 | Microsoft Corporation | Network load balancing with connection manipulation |
US7613822B2 (en) * | 2003-06-30 | 2009-11-03 | Microsoft Corporation | Network load balancing with session information |
US20050097353A1 (en) * | 2003-10-10 | 2005-05-05 | Bea Systems, Inc. | Policy analysis tool |
US20050102536A1 (en) * | 2003-10-10 | 2005-05-12 | Bea Systems, Inc. | Dynamically configurable distributed security system |
US7778422B2 (en) | 2004-02-27 | 2010-08-17 | Microsoft Corporation | Security associations for devices |
US7656885B2 (en) * | 2004-03-12 | 2010-02-02 | Sybase 365, Inc. | Intermediary content gateway system and method |
US20050251503A1 (en) * | 2004-04-13 | 2005-11-10 | Bea Systems, Inc. | System and method for content and schema versioning |
US20050240714A1 (en) * | 2004-04-13 | 2005-10-27 | Bea Systems, Inc. | System and method for virtual content repository deployment |
US7580953B2 (en) * | 2004-04-13 | 2009-08-25 | Bea Systems, Inc. | System and method for schema lifecycles in a virtual content repository that integrates a plurality of content repositories |
US20050246529A1 (en) | 2004-04-30 | 2005-11-03 | Microsoft Corporation | Isolated persistent identity storage for authentication of computing devies |
US20050256899A1 (en) * | 2004-05-14 | 2005-11-17 | Bea Systems, Inc. | System and method for representing hierarchical data structures |
US20050256906A1 (en) * | 2004-05-14 | 2005-11-17 | Bea Systems, Inc. | Interface for portal and webserver administration-efficient updates |
US7346633B2 (en) * | 2004-06-10 | 2008-03-18 | Sybase, Inc. | System providing methodology for replication subscription resolution |
US9245266B2 (en) | 2004-06-16 | 2016-01-26 | Callahan Cellular L.L.C. | Auditable privacy policies in a distributed hierarchical identity management system |
US8527752B2 (en) | 2004-06-16 | 2013-09-03 | Dormarke Assets Limited Liability | Graduated authentication in an identity management system |
US8135861B1 (en) * | 2004-10-06 | 2012-03-13 | Emc Corporation | Backup proxy |
US7543069B2 (en) * | 2004-10-18 | 2009-06-02 | International Business Machines Corporation | Dynamically updating session state affinity |
US8341288B2 (en) * | 2004-10-22 | 2012-12-25 | Cisco Technology, Inc. | Mechanism for sharing resources among different senders and receivers |
US7783670B2 (en) * | 2004-11-18 | 2010-08-24 | Bea Systems, Inc. | Client server conversion for representing hierarchical data structures |
US20060146812A1 (en) * | 2004-12-30 | 2006-07-06 | Lexmark International, Inc. | Methods and systems for routing data using a destination server |
US7802144B2 (en) | 2005-04-15 | 2010-09-21 | Microsoft Corporation | Model-based system monitoring |
US8489728B2 (en) | 2005-04-15 | 2013-07-16 | Microsoft Corporation | Model-based system monitoring |
US7797147B2 (en) | 2005-04-15 | 2010-09-14 | Microsoft Corporation | Model-based system monitoring |
US7487433B2 (en) * | 2005-06-10 | 2009-02-03 | Microsoft Corporation | Exception handling in content based routing solutions |
US9450908B2 (en) * | 2005-06-23 | 2016-09-20 | Go Daddy Operating Company, LLC | Routing DNS system and method for shared domain name |
US8706816B2 (en) * | 2005-06-24 | 2014-04-22 | Go Daddy Operating Company, LLC | System and method for email delivery for shared domain name |
US20050289242A1 (en) * | 2005-06-24 | 2005-12-29 | The Go Daddy Group, Inc. | Resolving access to content associated with shared domain name using routing website |
TWI314823B (en) * | 2005-06-24 | 2009-09-11 | Era Digital Media Co | Distributed streaming server |
US8549513B2 (en) | 2005-06-29 | 2013-10-01 | Microsoft Corporation | Model-based virtual system provisioning |
US8015233B2 (en) * | 2005-09-13 | 2011-09-06 | International Business Machines Corporation | Method for handling asynchronous database transactions in a web based environment |
US7818344B2 (en) | 2005-09-26 | 2010-10-19 | Bea Systems, Inc. | System and method for providing nested types for content management |
US7953734B2 (en) * | 2005-09-26 | 2011-05-31 | Oracle International Corporation | System and method for providing SPI extensions for content management system |
US7917537B2 (en) | 2005-09-26 | 2011-03-29 | Oracle International Corporation | System and method for providing link property types for content management |
US7752205B2 (en) | 2005-09-26 | 2010-07-06 | Bea Systems, Inc. | Method and system for interacting with a virtual content repository |
JP2007094610A (en) * | 2005-09-28 | 2007-04-12 | Hitachi Ltd | Computer system |
US7941309B2 (en) | 2005-11-02 | 2011-05-10 | Microsoft Corporation | Modeling IT operations/policies |
JP4377369B2 (en) * | 2005-11-09 | 2009-12-02 | 株式会社日立製作所 | Resource allocation arbitration device and resource allocation arbitration method |
GB0601939D0 (en) * | 2006-01-31 | 2006-03-15 | Speed Trap Com Ltd | Website monitoring and cookie setting |
EP1979839B1 (en) * | 2006-01-31 | 2014-01-08 | Speed-trap.com Ltd. | Website monitoring and cookie setting |
US20070288466A1 (en) * | 2006-05-02 | 2007-12-13 | Mypoints.Com Inc. | System and method for evenly distributing data across a distributed member architecture utilizing a home silo |
US7783763B2 (en) * | 2006-06-06 | 2010-08-24 | International Business Machines Corporation | Managing stateful data in a partitioned application server environment |
US20080077982A1 (en) * | 2006-09-22 | 2008-03-27 | Bea Systems, Inc. | Credential vault encryption |
US8463852B2 (en) | 2006-10-06 | 2013-06-11 | Oracle International Corporation | Groupware portlets for integrating a portal with groupware systems |
US7532134B2 (en) | 2007-03-12 | 2009-05-12 | Citrix Systems, Inc. | Systems and methods for sharing compression histories between multiple devices |
US8255570B2 (en) | 2007-03-12 | 2012-08-28 | Citrix Systems, Inc. | Systems and methods of compression history expiration and synchronization |
US7619545B2 (en) | 2007-03-12 | 2009-11-17 | Citrix Systems, Inc. | Systems and methods of using application and protocol specific parsing for compression |
US7460038B2 (en) * | 2007-03-12 | 2008-12-02 | Citrix Systems, Inc. | Systems and methods of clustered sharing of compression histories |
US7865585B2 (en) * | 2007-03-12 | 2011-01-04 | Citrix Systems, Inc. | Systems and methods for providing dynamic ad hoc proxy-cache hierarchies |
US7827237B2 (en) | 2007-03-12 | 2010-11-02 | Citrix Systems, Inc. | Systems and methods for identifying long matches of data in a compression history |
US8699349B2 (en) * | 2007-10-26 | 2014-04-15 | Microsoft Corporation | Multi-factor optimized routing |
US8613039B2 (en) * | 2008-06-03 | 2013-12-17 | International Business Machines Corporation | Automated correction and reporting for dynamic web applications |
CN101686245B (en) * | 2008-09-28 | 2014-06-11 | 国际商业机器公司 | Method and system for isolating hypertext transfer protocol session |
US8032930B2 (en) * | 2008-10-17 | 2011-10-04 | Intuit Inc. | Segregating anonymous access to dynamic content on a web server, with cached logons |
JP5458688B2 (en) * | 2009-03-19 | 2014-04-02 | 富士通株式会社 | Uniqueness guarantee support program, service providing system, and uniqueness guarantee realization method |
JP4810598B2 (en) * | 2009-08-03 | 2011-11-09 | シャープ株式会社 | Multifunction machine and system |
US8719223B2 (en) | 2010-05-06 | 2014-05-06 | Go Daddy Operating Company, LLC | Cloud storage solution for reading and writing files |
US8867529B2 (en) | 2010-09-20 | 2014-10-21 | Cisco Technology, Inc. | System and method for providing a fate sharing identifier in a network environment |
US9928091B2 (en) * | 2010-09-30 | 2018-03-27 | Microsoft Technology Licensing, Llc | Techniques for streaming virtual machines from a server to a host |
US20130054817A1 (en) * | 2011-08-29 | 2013-02-28 | Cisco Technology, Inc. | Disaggregated server load balancing |
US8538065B2 (en) | 2011-09-20 | 2013-09-17 | Go Daddy Operating Company, LLC | Systems for verifying person's identity through person's social circle using person's photograph |
US8522147B2 (en) | 2011-09-20 | 2013-08-27 | Go Daddy Operating Company, LLC | Methods for verifying person's identity through person's social circle using person's photograph |
US9729631B2 (en) | 2011-09-30 | 2017-08-08 | Apple Inc. | Asynchronous data manipulation |
US8838808B2 (en) * | 2011-09-30 | 2014-09-16 | Apple Inc. | Asynchronous communication in web applications |
US8782127B2 (en) * | 2011-09-30 | 2014-07-15 | Apple Inc. | Notification based web applications |
US8788627B2 (en) * | 2011-09-30 | 2014-07-22 | Apple Inc. | Interactive web application framework |
US9106663B2 (en) * | 2012-02-01 | 2015-08-11 | Comcast Cable Communications, Llc | Latency-based routing and load balancing in a network |
US8738604B2 (en) | 2012-03-30 | 2014-05-27 | Go Daddy Operating Company, LLC | Methods for discovering sensitive information on computer networks |
US8738605B2 (en) | 2012-03-30 | 2014-05-27 | Go Daddy Operating Company, LLC | Systems for discovering sensitive information on computer networks |
US9450882B2 (en) | 2012-04-23 | 2016-09-20 | Cisco Technology, Inc. | Method and apparatus for supporting call admission control using graph assembly and fate-share identifiers |
US9438659B2 (en) | 2012-06-21 | 2016-09-06 | Go Daddy Operating Company, LLC | Systems for serving website content according to user status |
US9141669B2 (en) | 2013-01-22 | 2015-09-22 | Go Daddy Operating Company, LLC | Configuring an origin server content delivery using a pulled data list |
US9160809B2 (en) | 2012-11-26 | 2015-10-13 | Go Daddy Operating Company, LLC | DNS overriding-based methods of accelerating content delivery |
US9384208B2 (en) | 2013-01-22 | 2016-07-05 | Go Daddy Operating Company, LLC | Configuring a cached website file removal using a pulled data list |
US9438493B2 (en) | 2013-01-31 | 2016-09-06 | Go Daddy Operating Company, LLC | Monitoring network entities via a central monitoring system |
US9720992B2 (en) * | 2013-11-22 | 2017-08-01 | Sap Se | DML replication with logical log shipping |
JP6409438B2 (en) * | 2014-09-19 | 2018-10-24 | 株式会社リコー | Session control system, communication terminal, communication system, session control method, and program |
GB2533116A (en) * | 2014-12-10 | 2016-06-15 | Ibm | Query dispatching system and method |
US10193867B2 (en) | 2015-05-27 | 2019-01-29 | Ping Identity Corporation | Methods and systems for API proxy based adaptive security |
WO2018030924A1 (en) * | 2016-08-11 | 2018-02-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and cloud management node for managing a data processing task |
US10587580B2 (en) | 2016-10-26 | 2020-03-10 | Ping Identity Corporation | Methods and systems for API deception environment and API traffic control and security |
US10699010B2 (en) | 2017-10-13 | 2020-06-30 | Ping Identity Corporation | Methods and apparatus for analyzing sequences of application programming interface traffic to identify potential malicious actions |
EP3678348A1 (en) | 2019-01-04 | 2020-07-08 | Ping Identity Corporation | Methods and systems for data traffic based adpative security |
CN112929210B (en) * | 2021-01-25 | 2023-04-18 | 城云科技(中国)有限公司 | Method and system for gateway routing application plug-in built on WebFlux framework and application of gateway routing application plug-in |
US20230401230A1 (en) * | 2022-06-09 | 2023-12-14 | Salesforce, Inc. | Database systems and related replication monitoring methods |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5655117A (en) * | 1994-11-18 | 1997-08-05 | Oracle Corporation | Method and apparatus for indexing multimedia information streams |
US5832495A (en) * | 1996-07-08 | 1998-11-03 | Survivors Of The Shoah Visual History Foundation | Method and apparatus for cataloguing multimedia data |
US5956716A (en) * | 1995-06-07 | 1999-09-21 | Intervu, Inc. | System and method for delivery of video data over a computer network |
US6173322B1 (en) * | 1997-06-05 | 2001-01-09 | Silicon Graphics, Inc. | Network request distribution based on static rules and dynamic performance data |
US6584223B1 (en) * | 1998-04-02 | 2003-06-24 | Canon Kabushiki Kaisha | Image search apparatus and method |
Family Cites Families (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPS61253572A (en) | 1985-05-02 | 1986-11-11 | Hitachi Ltd | Load distributing system for loose coupling multi-processor system |
US5459837A (en) | 1993-04-21 | 1995-10-17 | Digital Equipment Corporation | System to facilitate efficient utilization of network resources in a computer network |
US5559764A (en) | 1994-08-18 | 1996-09-24 | International Business Machines Corporation | HMC: A hybrid mirror-and-chained data replication method to support high data availability for disk arrays |
US5774668A (en) | 1995-06-07 | 1998-06-30 | Microsoft Corporation | System for on-line service in which gateway computer uses service map which includes loading condition of servers broadcasted by application servers for load balancing |
US5603029A (en) | 1995-06-07 | 1997-02-11 | International Business Machines Corporation | System of assigning work requests based on classifying into an eligible class where the criteria is goal oriented and capacity information is available |
US5915095A (en) | 1995-08-08 | 1999-06-22 | Ncr Corporation | Method and apparatus for balancing processing requests among a plurality of servers based on measurable characteristics off network node and common application |
GB2305747A (en) | 1995-09-30 | 1997-04-16 | Ibm | Load balancing of connections to parallel servers |
JPH09167141A (en) | 1995-12-18 | 1997-06-24 | Hitachi Ltd | Load distribution control method |
US5828847A (en) | 1996-04-19 | 1998-10-27 | Storage Technology Corporation | Dynamic server switching for maximum server availability and load balancing |
US5894554A (en) * | 1996-04-23 | 1999-04-13 | Infospinner, 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 |
US5890156A (en) | 1996-05-02 | 1999-03-30 | Alcatel Usa, Inc. | Distributed redundant database |
US5774660A (en) | 1996-08-05 | 1998-06-30 | Resonate, Inc. | World-wide-web server with delayed resource-binding for resource-based load balancing on a distributed resource multi-node network |
US5864535A (en) | 1996-09-18 | 1999-01-26 | International Business Machines Corporation | Network server having dynamic load balancing of messages in both inbound and outbound directions |
US6014660A (en) | 1996-12-09 | 2000-01-11 | Sun Microsystems, Inc. | Method and apparatus for client-sensitive name resolution using DNS |
US5933606A (en) | 1997-02-19 | 1999-08-03 | International Business Machines Corporation | Dynamic link page retargeting using page headers |
US5933596A (en) | 1997-02-19 | 1999-08-03 | International Business Machines Corporation | Multiple server dynamic page link retargeting |
US5991808A (en) | 1997-06-02 | 1999-11-23 | Digital Equipment Corporation | Task processing optimization in a multiprocessor system |
US6263368B1 (en) * | 1997-06-19 | 2001-07-17 | Sun Microsystems, Inc. | Network load balancing for multi-computer server by counting message packets to/from multi-computer server |
US6006264A (en) | 1997-08-01 | 1999-12-21 | Arrowpoint Communications, Inc. | Method and system for directing a flow between a client and a server |
US6070191A (en) * | 1997-10-17 | 2000-05-30 | Lucent Technologies Inc. | Data distribution techniques for load-balanced fault-tolerant web access |
US6041307A (en) | 1998-01-23 | 2000-03-21 | Lucent Technologies Inc. | Technique for effectively managing resources in a network |
US6076108A (en) * | 1998-03-06 | 2000-06-13 | I2 Technologies, Inc. | System and method for maintaining a state for a user session using a web system having a global session server |
US6098093A (en) * | 1998-03-19 | 2000-08-01 | International Business Machines Corp. | Maintaining sessions in a clustered server environment |
US6006259A (en) | 1998-11-20 | 1999-12-21 | Network Alchemy, Inc. | Method and apparatus for an internet protocol (IP) network clustering system |
US6405252B1 (en) * | 1999-11-22 | 2002-06-11 | Speedera Networks, Inc. | Integrated point of presence server network |
-
2000
- 2000-12-05 WO PCT/US2000/042786 patent/WO2001044894A2/en active Application Filing
- 2000-12-05 AU AU47179/01A patent/AU4717901A/en not_active Abandoned
- 2000-12-05 US US09/730,259 patent/US6598077B2/en not_active Expired - Fee Related
-
2003
- 2003-03-07 US US10/384,284 patent/US20030158951A1/en not_active Abandoned
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5655117A (en) * | 1994-11-18 | 1997-08-05 | Oracle Corporation | Method and apparatus for indexing multimedia information streams |
US5956716A (en) * | 1995-06-07 | 1999-09-21 | Intervu, Inc. | System and method for delivery of video data over a computer network |
US5832495A (en) * | 1996-07-08 | 1998-11-03 | Survivors Of The Shoah Visual History Foundation | Method and apparatus for cataloguing multimedia data |
US6173322B1 (en) * | 1997-06-05 | 2001-01-09 | Silicon Graphics, Inc. | Network request distribution based on static rules and dynamic performance data |
US6584223B1 (en) * | 1998-04-02 | 2003-06-24 | Canon Kabushiki Kaisha | Image search apparatus and method |
Cited By (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150134845A1 (en) * | 2000-05-31 | 2015-05-14 | Ganas Llc | Object Oriented Communication Among Platform Independent Systems over Networks Using SOAP |
US7916631B2 (en) * | 2000-11-28 | 2011-03-29 | Microsoft Corporation | Load balancing in set top cable box environment |
US20050185596A1 (en) * | 2000-11-28 | 2005-08-25 | Navic Systems, Inc. | Load balancing in set top cable box environment |
US20030028669A1 (en) * | 2001-07-06 | 2003-02-06 | Alcatel | Method and system for routing logging a request |
US20030120722A1 (en) * | 2001-12-20 | 2003-06-26 | Forkner Damien R. | Persistent process software architecture |
US20050025051A1 (en) * | 2003-08-01 | 2005-02-03 | Roeder Michael T. | Automated router load balancing |
US8045566B2 (en) * | 2003-08-01 | 2011-10-25 | Hewlett-Packard Development Company, L.P. | Automated router load balancing |
US20050038833A1 (en) * | 2003-08-14 | 2005-02-17 | Oracle International Corporation | Managing workload by service |
US7747717B2 (en) * | 2003-08-14 | 2010-06-29 | Oracle International Corporation | Fast application notification in a clustered computing system |
US20050038772A1 (en) * | 2003-08-14 | 2005-02-17 | Oracle International Corporation | Fast application notification in a clustered computing system |
US7853579B2 (en) | 2003-08-14 | 2010-12-14 | Oracle International Corporation | Methods, systems and software for identifying and managing database work |
US7664847B2 (en) | 2003-08-14 | 2010-02-16 | Oracle International Corporation | Managing workload by service |
US20050080885A1 (en) * | 2003-09-26 | 2005-04-14 | Imran Ahmed | Autonomic monitoring for web high availability |
US7996529B2 (en) | 2003-09-26 | 2011-08-09 | International Business Machines Corporation | System for autonomic monitoring for web high availability |
US7689685B2 (en) * | 2003-09-26 | 2010-03-30 | International Business Machines Corporation | Autonomic monitoring for web high availability |
US20100180002A1 (en) * | 2003-09-26 | 2010-07-15 | International Business Machines Corporation | System for autonomic monitoring for web high availability |
US20110029683A1 (en) * | 2004-03-25 | 2011-02-03 | International Business Machines Corporation | Real-time Attribute Processor and Syntax Schema for Directory Access Protocol Services |
US8145666B2 (en) | 2004-03-25 | 2012-03-27 | International Business Machines Corporation | Real-time attribute processor and syntax schema for directory access protocol services |
US7840588B2 (en) | 2004-03-25 | 2010-11-23 | International Business Machines Corporation | Real-time attribute processor and syntax schema for directory access protocol services |
US20060089965A1 (en) * | 2004-10-26 | 2006-04-27 | International Business Machines Corporation | Dynamic linkage of an application server and a Web server |
US8639846B2 (en) | 2005-06-29 | 2014-01-28 | Visa U.S.A. Inc. | Adaptive gateway for switching transactions and data on unreliable networks using context-based rules |
US9215196B2 (en) | 2005-06-29 | 2015-12-15 | Visa U.S.A., Inc. | Schema-based dynamic parse/build engine for parsing multi-format messages |
US20100211938A1 (en) * | 2005-06-29 | 2010-08-19 | Visa U.S.A., Inc. | Schema-based dynamic parse/build engine for parsing multi-format messages |
US20070005613A1 (en) * | 2005-06-29 | 2007-01-04 | Visa U.S.A., Inc. | Schema-based dynamic parse/build engine for parsing multi-format messages |
US8555262B2 (en) | 2005-06-29 | 2013-10-08 | Visa U.S.A. Inc. | Schema-based dynamic parse/build engine for parsing multi-format messages |
US7694287B2 (en) | 2005-06-29 | 2010-04-06 | Visa U.S.A. | Schema-based dynamic parse/build engine for parsing multi-format messages |
US20110047294A1 (en) * | 2005-06-29 | 2011-02-24 | Visa U.S.A., Inc. | Adaptive gateway for switching transactions and data on unreliable networks using context-based rules |
US9756001B2 (en) | 2005-06-29 | 2017-09-05 | Visa U.S.A. | Schema-based dynamic parse/build engine for parsing multi-format messages |
US7774402B2 (en) * | 2005-06-29 | 2010-08-10 | Visa U.S.A. | Adaptive gateway for switching transactions and data on unreliable networks using context-based rules |
US20070005774A1 (en) * | 2005-06-29 | 2007-01-04 | Visa U.S.A., Inc. | Adaptive gateway for switching transactions and data on unreliable networks using context-based rules |
US20080022386A1 (en) * | 2006-06-08 | 2008-01-24 | Shevchenko Oleksiy Yu | Security mechanism for server protection |
US20080091806A1 (en) * | 2006-10-11 | 2008-04-17 | Jinmei Shen | Dynamic On-Demand Clustering |
US8713186B2 (en) | 2007-03-13 | 2014-04-29 | Oracle International Corporation | Server-side connection resource pooling |
US8352634B2 (en) * | 2007-04-06 | 2013-01-08 | International Business Machines Corporation | On-demand propagation of routing information in distributed computing system |
US20080250099A1 (en) * | 2007-04-06 | 2008-10-09 | Jinmei Shen | On-Demand Propagation of Routing Information in Distributed Computing System |
US20110179181A1 (en) * | 2008-06-03 | 2011-07-21 | Ian Gordan Elz | Identifying User Role in IP Multimedia Subsystem |
US8583804B2 (en) * | 2008-06-03 | 2013-11-12 | Telefonaktiebolaget L M Ericsson (Publ) | Identifying user role in IP multimedia subsystem |
WO2010120549A3 (en) * | 2009-03-31 | 2011-01-13 | Ecrio, Inc. | System, method and apparatus for providing functions to applications on a digital electronic device |
WO2010120549A2 (en) * | 2009-03-31 | 2010-10-21 | Ecrio, Inc. | System, method and apparatus for providing functions to applications on a digital electronic device |
US20100257539A1 (en) * | 2009-03-31 | 2010-10-07 | Krishnakumar Narayanan | System, method and apparatus for providing functions to applications on a digital electronic device |
US8543508B2 (en) | 2010-07-09 | 2013-09-24 | Visa International Service Association | Gateway abstraction layer |
US9846905B2 (en) | 2010-07-09 | 2017-12-19 | Visa International Service Association | Gateway abstraction layer |
US9298455B1 (en) * | 2013-03-15 | 2016-03-29 | Instart Logic, Inc. | Provisional execution of dynamic content component |
US9363329B1 (en) * | 2013-03-15 | 2016-06-07 | Instart Logic, Inc. | Identifying correlated components of dynamic content |
US9229999B2 (en) | 2013-03-15 | 2016-01-05 | International Business Machines Corporation | Using average replication latency to influence routing query transactions |
US10091289B2 (en) | 2013-03-15 | 2018-10-02 | Instart Logic, Inc. | Provisional execution of dynamic content component |
US9813480B2 (en) | 2015-01-08 | 2017-11-07 | Instart Logic, Inc. | Placeholders for dynamic components in HTML streaming |
US9998521B2 (en) | 2015-01-08 | 2018-06-12 | Instart Logic, Inc. | HTML streaming |
US10382520B2 (en) | 2015-01-08 | 2019-08-13 | Instart Logic, Inc. | Placeholders for dynamic components in HTML streaming |
US10425464B2 (en) | 2015-01-08 | 2019-09-24 | Instart Logic, Inc. | Adaptive learning periods in HTML streaming |
US10931731B2 (en) | 2015-01-08 | 2021-02-23 | Akamai Technologies, Inc. | Adaptive learning periods in HTML streaming |
US10474653B2 (en) | 2016-09-30 | 2019-11-12 | Oracle International Corporation | Flexible in-memory column store placement |
Also Published As
Publication number | Publication date |
---|---|
US6598077B2 (en) | 2003-07-22 |
AU4717901A (en) | 2001-06-25 |
WO2001044894A3 (en) | 2002-05-10 |
US20010039586A1 (en) | 2001-11-08 |
WO2001044894A2 (en) | 2001-06-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6598077B2 (en) | System and method for dynamic content routing | |
US7509407B2 (en) | Load balancing technique implemented in a data network device utilizing a data cache | |
US7197547B1 (en) | Load balancing technique implemented in a data network device utilizing a data cache | |
US7200665B2 (en) | Allowing requests of a session to be serviced by different servers in a multi-server data service system | |
KR100511687B1 (en) | The intelligent Traffic Managemet system for among the networks and method thereof | |
US6907463B1 (en) | System and method for enabling file transfers executed in a network environment by a software program | |
US7543069B2 (en) | Dynamically updating session state affinity | |
US20020073211A1 (en) | System and method for securely communicating between application servers and webservers | |
US20070158416A1 (en) | Method of delivering web content to fuel dispenser | |
US11095580B2 (en) | Instant message (IM) routing to a virtual user consisting of a group of possible sub-users associated with a common IM identity | |
US11741174B2 (en) | Direct leg access for proxy web scraping | |
JP2002540677A (en) | Data network load management | |
US8166100B2 (en) | Cross site, cross domain session sharing without database replication | |
US8250220B2 (en) | Generalized proximity service | |
US8738513B2 (en) | Apparatus and method for managing account information | |
EP4227828A1 (en) | Web scraping through use of proxies, and applications thereof | |
EP1810188A2 (en) | Apparatus and method for building conjoined computer systems | |
US20230018983A1 (en) | Traffic counting for proxy web scraping | |
US6819656B2 (en) | Session based scheduling scheme for increasing server capacity | |
WO2023280593A1 (en) | Web scraping through use of proxies, and applications thereof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |