DRIVING A USER EXPERIENCE OF A WEB APPLICATION USING RULES THAT ESTABLISH OR CHANGE REQUESTS BASED ON USER BEHAVIOR

• US 20120173607A1
• Filed: 12/30/2010
• Published: 07/05/2012
• Est. Priority Date: 12/30/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: CONNAN, MATTHIEU, GHAITH, SHADI, GHOORBIN, KIRANSINGH, MANNING, DAVID, MCGLOIN, MARK
• Granted Patent: US 9,483,570 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/957 Browsing optimisation, e.g. caching or content distillation
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: H04L 67/00 Network arrangements or protocols for supporting network services or applications user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

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.

Claims

1. A method comprising:

receiving a set of one or more RESTful requests from a client computing device, where each of the RESTful requests includes a resource identifier for a Web server;

determining at least one pattern from analyzing the set of RESTful requests;

comparing the pattern against a plurality of previously established patterns, wherein said plurality of previously established patterns are each indexed against a resource identifier of for the Web server;

in response to the comparing, matching the pattern to a corresponding previously established pattern; and

conveying a pattern RESTful request to the Web server for a Web resource identified by a matched resource identifier, wherein said matched resource identifier is the resource identifier that is indexed against the previously established pattern, 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, 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 a user of the client computing device.

2. The method of claim 1, wherein the Web resource served by the Web server responsive to receipt of the pattern RESTful request causes a change to layout elements of a user interface that is displayed in a Web browser of the client computing device.

3. The method of claim 1, wherein the determined pattern indicates a user interest that is inferred from the set of RESTful requests and that is inferred from timing between the set of RESTful requests, wherein the pattern RESTful request is a request to the Web server for additional information specific to the user interest.

4. The method of claim 1, wherein said set of RESTful requests comprise a plurality of RESTful requests, wherein each of the RESTful requests is for a Web page of a Web application hosted on the Web server.

5. The method of claim 4, wherein the pattern is indicative of a user'"'"'s interest in a business offering available through the Web application, wherein the matched resource identifier is an identifier for the business offering.

6. The method of claim 1, wherein the pattern RESTful request is a modification of a RESTful request from the client computing device, which is provided to the Web server instead of providing the RESTful request from the client computing device.

7. The method of claim 1, wherein the receiving, determining, comparing, matching, and conveying are performed by a network element, which executes within a network to which the client computing device and the Web server are communicatively linked, wherein the network element receives the set of RESTful requests from the client computing device and selectively routes the RESTful requests of the set to the Web server.

8. The method of claim 1, wherein the receiving, determining, comparing, matching, and conveying are performed by a request pre-processing software component executing on the Web server.

9. The method of claim 1, wherein the receiving, determining, comparing, matching, and conveying are performed by a client-side program executing on the client-computing device.

10. The method of claim 1, wherein each of the RESTful requests is a HTTP request.

11. The method of claim 1, further comprising:

routing each of the received set of one or more RESTful requests from the client computing device to the Web server, wherein each of the RESTful requests is a request for Web application content from a Web application hosted by the Web server.

12. The method of claim 1, wherein the pattern is indicative of user interest in a business offering available via a Web application hosted by the Web server, wherein the resource corresponding to the matched resource identifier comprises content related specifically to the user interest, wherein the Web resource served by the Web server in response to the pattern RESTful request causes a user interface of a Web browser of the client computing device to display the content that is related to the user interest.

13. A computer program product comprising a computer readable storage medium having computer usable program code embodied therewith, the computer usable program code comprising:

computer usable program code stored on a storage medium that upon being executed by a processor is operable to receive a set of one or more RESTful requests from a client computing device, where each of the RESTful requests includes a resource identifier for a Web server;

computer usable program code stored on a storage medium that upon being executed by a processor is operable to determine at least one pattern from analyzing the set of RESTful requests;

computer usable program code stored on a storage medium that upon being executed by a processor is operable to compare the pattern against a plurality of previously established patterns, wherein said plurality of previously established patterns are each indexed against a resource identifier of for the Web server;

computer usable program code stored on a 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 storage medium that upon being executed by a processor is operable to convey a pattern RESTful request to the Web server for a Web resource identified by a matched resource identifier, wherein said matched resource identifier is the resource identifier that is indexed against the previously established pattern, 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, 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 a user of the client computing device.

14. The computer program product of claim 13, wherein the determined at least one pattern indicates a user interest that is inferred from the set of RESTful requests and timing between the set of RESTful requests, wherein the pattern RESTful requests is a request to receive additional information specific to the user interest from the Web server, wherein said set of RESTful requests comprise a plurality of RESTful requests, wherein each of the RESTful requests is for a Web page of a Web application hosted on the Web server.

15. The computer program product of claim 13, wherein the receiving, determining, comparing, matching, and conveying are performed by a network element, which executes within a network to which the client computing device and the Web server are communicatively linked, wherein the network element receives the set of RESTful requests from the client computing device and selectively routes the RESTful requests of the set to the Web server.

16. A method comprising:

routing a plurality of HTTP requests for Web application content from a client computing device to a Web server;

analyzing the routed HTTP requests for patterns indicative of user interest in a business offering available via the Web application; and

conveying an unrequested HTTP 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.

17. The method of claim 16, further comprising:

at the end of each application session involving the Web application, storing user interest information gleaned from the HTTP requests in a user specific profile; and

consulting the user specific profile for each session between a user and the Web application to improve an ability to determine the user interest and to responsively modify HTTP requests to the Web server in accordance with this determined user interest.

18. The method of claim 16, further comprising:

organizing the Web application so that a plurality of different business functions are associated with different resource identifiers; and

parsing the HTTP requests to determine business functions of interest to a user of the client computing device during the analyzing of the routed HTTP requests.

19. The method of claim 16, further comprising:

modifying at least one parameter of a HTTP requests from the client computing device based on the user interest; and

routing the modified HTTP request to the Web server.

20. The method of claim 16, wherein the analyzing of the routed HTTP requests further comprises:

determining at least one pattern from analyzing the routed HTTP requests;

comparing the at least one pattern against a plurality of previously established patterns, wherein said plurality of previously established patterns are each indexed against a resource identifier of for the Web server; and

in response to the comparing, matching the at least one pattern to a corresponding previously established pattern, wherein the unrequested HTTP request is for a Web resource identified by a matched resource identifier, wherein the matched resource identifier is the resource identifier that is indexed against the at least one previously established pattern that was matched.