Intelligent caching routers
First Claim
1. In an application service provider (ASP) computing environment wherein a client interacts with a remote server over a shared network, a method of increasing transaction reliability, comprising the steps of:
- maintaining a list of critical transactions;
locally caching at least certain processing capabilities associated with the application;
monitoring requests from the client to determine if a request relates to one of the critical transactions; and
, if so;
processing that transaction locally and returning a response directly to the client.
1 Assignment
0 Petitions
Accused Products
Abstract
An intelligent caching router (ICR) balances the cost-saving and functionality-enhancing benefits of the application-service-provider (ASP) model of software delivery against the inherent risks of relying on networked computing. In so doing, the ICR makes the ASP model practical for services that require extremely high levels of reliability and availability. The ICR is inserted functionally between a (thin) client and the network (i.e., Internet, intranet or extranet) and performs certain operations, including the logging of “mission-critical” application state data; network connectivity monitoring; traditional backup routing features; mission-critical server emulation; and server resynchronization upon reconnection. When networking problems are detected, the ICR initially takes steps to try and restore connectivity. In taking such actions, the ICR is largely behaving as a traditional intelligent network router. However, when such traditional backup routing fails, the ICR begins to act as a surrogate for the unreachable remote server on which the application service depends. In particular, for the application subset that the service providers have deemed “mission critical,” the ICR makes application-specific responses to permit operations to continue, and logging the requests and response it has issued. When the communications link is restored, the ICR will re-synchronize with the remote server and then return to its normal “passive” operation. The invention is particularly suited to electronic commerce transactions, since accounting, crediting or debiting may be considered critical transactions, whereas other forms of updating, reporting, and the like are typically less critical. One disclosed example shows the role of an ICR in a point-of-sale application.
-
Citations
27 Claims
-
1. In an application service provider (ASP) computing environment wherein a client interacts with a remote server over a shared network, a method of increasing transaction reliability, comprising the steps of:
-
maintaining a list of critical transactions;
locally caching at least certain processing capabilities associated with the application;
monitoring requests from the client to determine if a request relates to one of the critical transactions; and
, if so;
processing that transaction locally and returning a response directly to the client. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26)
-
-
13. In a network computing environment wherein a client interacts with a remote server providing access to an application, an intelligent caching router comprising:
-
a component containing software, hardware, or both, situated proximate to the location of the client and functioning as an interface to the network, the component storing a list of critical transactions and at least some of the processing capabilities associated with the application, the component being operative to perform the following functions;
a) monitor requests from the client to determine if a request relates to one of the critical transactions; and
, if so;
b) process that transaction locally and returning a response directly to the client.
-
-
27. In an application service provider (ASP) computing environment wherein a client interacts with a remote server over a shared network, the improvement comprising:
an intelligent caching router (ICR) inserted functionally between the client and the network, such that when conventional backup routing, fails, the ICR begins to act as a surrogate for the unreachable remote server on which the application service depends.
Specification