Driving a user experience of a web application using rules that establish or change requests based on user behavior
First Claim
1. A method comprising:
- receiving a set of three or more RESTful requests from a client computing device, wherein a third request of the RESTful requests are received after a first two of the RESTful requests have been fulfilled, wherein at least the third request includes a resource identifier for a Web server running a Web application, wherein the RESTful requests include RESTful commands that are stateless, wherein the Web application itself does not persist state information and is implemented in a stateless fashion;
determining at least one user behavior pattern from analyzing the first two RESTful requests;
in responding to the third request, comparing the user behavior pattern against a plurality of previously established patterns mapped to Web application functions, wherein said plurality of previously established patterns are each indexed against a resource identifier for the Web server which is mapped to a corresponding function of the Web application;
in response to the comparing, matching the user behavior pattern to a corresponding previously established pattern; and
in response to the third request and in response to the matching, conveying a pattern RESTful request to the Web server for a Web resource identified by the matched resource identifier, wherein said matched resource identifier is the resource identifier that is indexed against the previously established pattern and that is mapped to the corresponding function of the Web application, wherein the pattern RESTful request causes the Web server to serve the Web resource identified by the matched resource identifier to the client computing device such that the Web application in responding to the third request has been dynamically adjusted for user behavior as determined from the user behavior pattern from analyzing the first two RESTful requests, wherein the pattern RESTful request was not directly issued by a user of the client computing device, and wherein the matched resource identifier is for a resource not explicitly requested by the user of the client computing device, wherein the adjustments by the Web application for the user behavior are not dependent on code logic of the Web application itself.
1 Assignment
0 Petitions
Accused Products
Abstract
A set of hypertext transfer protocol (HTTP) requests for Web application content can be routed from a client computing device to a Web server. The routed HTTP requests can be analyzed for patterns indicative of user interest in a business offering available via the Web application. An unrequested HTTP request can be conveyed to the Web server for Web application content that was not explicitly requested from the client computing device. The Web server can convey a response to the unrequested HTTP request that provides content from the Web application related specifically to the user interest. The response can cause a user interface of a Web browser of the client computing device to display the content that is related to the user interest.
26 Citations
20 Claims
-
1. A method comprising:
-
receiving a set of three or more RESTful requests from a client computing device, wherein a third request of the RESTful requests are received after a first two of the RESTful requests have been fulfilled, wherein at least the third request includes a resource identifier for a Web server running a Web application, wherein the RESTful requests include RESTful commands that are stateless, wherein the Web application itself does not persist state information and is implemented in a stateless fashion; determining at least one user behavior pattern from analyzing the first two RESTful requests; in responding to the third request, comparing the user behavior pattern against a plurality of previously established patterns mapped to Web application functions, wherein said plurality of previously established patterns are each indexed against a resource identifier for the Web server which is mapped to a corresponding function of the Web application; in response to the comparing, matching the user behavior pattern to a corresponding previously established pattern; and in response to the third request and in response to the matching, conveying a pattern RESTful request to the Web server for a Web resource identified by the matched resource identifier, wherein said matched resource identifier is the resource identifier that is indexed against the previously established pattern and that is mapped to the corresponding function of the Web application, wherein the pattern RESTful request causes the Web server to serve the Web resource identified by the matched resource identifier to the client computing device such that the Web application in responding to the third request has been dynamically adjusted for user behavior as determined from the user behavior pattern from analyzing the first two RESTful requests, wherein the pattern RESTful request was not directly issued by a user of the client computing device, and wherein the matched resource identifier is for a resource not explicitly requested by the user of the client computing device, wherein the adjustments by the Web application for the user behavior are not dependent on code logic of the Web application itself. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A computer program product comprising a non-transitory computer readable storage medium having computer usable program code embodied therewith, the computer usable program code comprising:
-
computer usable program code stored on a non-transitory storage medium that upon being executed by a processor is operable to receive a set of three or more RESTful requests from a client computing device, wherein a third request of the RESTful requests are received after a first two of the RESTful requests have been fulfilled, wherein at least the third request includes a resource identifier for a Web server running a Web application, wherein the RESTful requests include RESTful commands that are stateless, wherein the Web application itself does not persist state information and is implemented in a stateless fashion; computer usable program code stored on a non-transitory storage medium that upon being executed by a processor is operable to determine at least one user behavior pattern from analyzing the first two RESTful requests; computer usable program code stored on a non-transitory storage medium that upon being executed by a processor is operable to, in response to the third request, compare the user behavior pattern against a plurality of previously established patterns mapped to Web application functions, wherein said plurality of previously established patterns are each indexed against a resource identifier for the Web server which is mapped to a corresponding function of the Web application; computer usable program code stored on a non-transitory storage medium that upon being executed by a processor is operable to, in response to the comparing, match the pattern to a corresponding previously established pattern; and computer usable program code stored on a non-transitory storage medium that upon being executed by a processor is operable to, in response to the third request and in response to the matching, convey a pattern RESTful request to the Web server for a Web resource identified by the matched resource identifier, wherein said matched resource identifier is the resource identifier that is indexed against the previously established pattern and that is mapped to the corresponding function of the Web application, wherein the pattern RESTful request causes the Web server to serve the Web resource identified by the matched resource identifier to the client computing device such that the Web application in responding to the third request has been dynamically adjusted for user behavior as determined from the user behavior pattern from analyzing the first two RESTful requests, wherein the pattern RESTful request was not directly issued by a user of the client computing device, and wherein the matched resource identifier is for a resource not explicitly requested by the user of the client computing device, wherein the adjustments by the Web application for the user behavior are not dependent on code logic of the Web application itself. - View Dependent Claims (14, 15)
-
-
16. A method comprising:
-
routing a plurality of HTTP requests for Web application content from a client computing device to a Web server, wherein a third request of the HTTP requests is received after a first two of the HTTP requests have been fulfilled, wherein the HTTP requests include commands that are stateless, wherein the Web application itself does not persist state information and is implemented in a stateless fashion, wherein the third request is directed to the Web server upon which the Web application runs; analyzing the first two requests for user behavior patterns indicative of user interest in a business offering available via the Web application; and in response to the third request and in response to results of the analyzing, conveying an unrequested HTTP request different from the third request to the Web server for Web application content that was not explicitly requested from the client computing device, where per the unrequested HTTP request, the Web server is to convey a response that provides content from the Web application related specifically to the user interest, which causes a user interface of a Web browser of the client computing device to display the content that is related to the user interest, wherein the unrequested HTTP request represents a modification of the third request adjusted for user interest determined by analyzing the first two requests, wherein content related to the user interest content is displayed to the user by the Web application which has made a dynamic adjustment of content provided, wherein the dynamic adjustment is not dependent on code logic of the Web application itself but results from execution of statelessly implemented Web application functions triggered by the unrequested HTTP request. - View Dependent Claims (17, 18, 19, 20)
-
Specification