SYSTEM FOR ENABLING RICH NETWORK APPLICATIONS

• US 20100306366A1
• Filed: 06/02/2009
• Published: 12/02/2010
• Est. Priority Date: 06/02/2009
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: PETRI, JOHN E., CRAGUN, BRIAN J.
• Granted Patent: US 9,497,248 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/30 Profiles
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34

Abstract

The present invention generally provides methods, systems and articles of manufacture that provide an autonomous system for enabling rich network applications. Embodiments of the invention may monitor an existing network application and generate a profile on the network application based on what responses and data updates are triggered by various requests from a user. Embodiments of the invention may refactor the existing network application into a rich network application based on the profile created for that network application.

Claims

1. A computer-implemented method of refactoring a web-based application, comprising:

monitoring a plurality of requests received from a client application interacting with the web-based application;

monitoring a generated response for each of the plurality of requests, wherein each generated response is a markup-language document generated in response to the request and is transmitted to the client application for rendering;

identifying at least one pattern between the plurality of requests and the generated responses, wherein the pattern shows a correlation between a first request and a corresponding generated response; and

refactoring the web-based application based on the at least one pattern, wherein the refactoring comprises;

generating a server component, wherein the server component is configured to generate a portion of one of the markup-language documents, and

generating a client component to embed in the markup-language document generated for the first request, wherein the client component is configured to invoke the server component to update at least a portion of the markup-language document corresponding to the first request.

2. The method of claim 1, wherein the identifying at least one pattern in the plurality of requests and the generated responses, comprises:

matching one or more parameters in the first request from the plurality of requests with portions of the generated response; and

identifying changes between the generated response and a markup-language document most recently rendered by the client application.

3. The method of claim 1, wherein identifying at least one pattern between the plurality of requests and the generated responses includes identifying a set of server-side data accessed in processing the request.

4. The method of claim 1, wherein the pattern identified in the first request is to update a portion of data retrieved from a database and rendered in a corresponding markup language document.

5. The method of claim 1, wherein the web-application includes at least a web server, an application server, and a database.

6. The method of claim 1, wherein generating a server component further comprising partitioning a page of the web-based application into one or more refactored pages, wherein the partitioning is based on the at least one pattern and wherein the client component is configured to invoke a corresponding refactored page to update at least a portion of the markup-language document corresponding to the first request.

7. The method of claim 1, wherein the web-based application is a Java 2 Enterprise Edition web application.

8. The method of claim 1, wherein the refactoring the web-based application includes refactoring the client application to interact with the web-based application using Asynchronous JavaScript and XML.

9. A computer-readable storage-medium containing a program which, when executed on a processor, performs an operation for refactoring a web-based application, the operation comprising:

monitoring a plurality of requests received from a client application interacting with the web-based application;

monitoring a generated response for each of the plurality of requests, wherein each generated response is a markup-language document generated in response to the request and is transmitted to the client application for rendering;

identifying at least one pattern between the plurality of requests and the generated responses, wherein the pattern shows a correlation between a first request and a corresponding generated response; and

refactoring the web-based application based on the at least one pattern, wherein the refactoring comprises;

generating a server component, wherein the server component is configured to generate a portion of one of the markup-language documents, and

generating a client component to embed in the markup-language document generated for the first request, wherein the client component is configured to invoke the server component to update at least a portion of the markup-language document corresponding to the first request.

10. The computer-readable storage-medium of claim 9, wherein the identifying at least one pattern in the plurality of requests and the generated responses, comprises:

matching one or more parameters in the first request from the plurality of requests with portions of the generated response; and

identifying changes between the generated response and a markup-language document most recently rendered by the client application.

11. The computer-readable storage-medium of claim 9, wherein identifying at least one pattern between the plurality of requests and the generated responses includes identifying a set of server-side data accessed in processing the request.

12. The computer-readable storage-medium of claim 9, wherein the pattern identified in the first request is to update a portion of data retrieved from a database and rendered in a corresponding markup language document.

13. The computer-readable storage-medium of claim 9, wherein the web-application includes at least a web server, an application server, and a database.

14. The computer-readable storage-medium of claim 9, wherein generating a server component further comprising partitioning a page of the web-based application into one or more refactored pages, wherein the partitioning is based on the at least one pattern and wherein the client component is configured to invoke a corresponding refactored page to update at least a portion of the markup-language document corresponding to the first request.

15. The computer-readable storage-medium of claim 9, wherein the web-based application is a Java 2 Enterprise Edition web application.

16. The computer-readable storage-medium of claim 9, wherein the refactoring the web-based application includes refactoring the client application to interact with the web-based application using Asynchronous JavaScript and XML.

17. A system, comprising:

a processor; and

a memory containing a program, which when executed by the processor, performs an operation for performs an operation for refactoring a web-based application, the operation comprising;

monitoring a plurality of requests received from a client application interacting with the web-based application,

monitoring a generated response for each of the plurality of requests, wherein each generated response is a markup-language document generated in response to the request and is transmitted to the client application for rendering,

identifying at least one pattern between the plurality of requests and the generated responses, wherein the pattern shows a correlation between a first request and a corresponding generated response, and

refactoring the web-based application based on the at least one pattern, wherein the refactoring comprises;

generating a server component, wherein the server component is configured to generate a portion of one of the markup-language documents; and

generating a client component to embed in the markup-language document generated for the first request, wherein the client component is configured to invoke the server component to update at least a portion of the markup-language document corresponding to the first request.

18. The system of claim 17, wherein the identifying at least one pattern in the plurality of requests and the generated responses, comprises:

matching one or more parameters in the first request from the plurality of requests with portions of the generated response; and

identifying changes between the generated response and a markup-language document most recently rendered by the client application.

19. The system of claim 17, wherein identifying at least one pattern between the plurality of requests and the generated responses includes identifying a set of server-side data accessed in processing the request.

20. The system of claim 17, wherein the pattern identified in the first request is to update a portion of data retrieved from a database and rendered in a corresponding markup language document.

21. The system of claim 17, wherein the web-application includes at least a web server, an application server, and a database.

22. The system of claim 17, wherein generating a server component further comprising partitioning a page of the web-based application into one or more refactored pages, wherein the partitioning is based on the at least one pattern and wherein the client component is configured to invoke a corresponding refactored page to update at least a portion of the markup-language document corresponding to the first request.

23. A computer-implemented method for refactoring an network application, comprising:

monitoring a first network application, wherein the first network application includes at least one client-side component configured to interact with at least one server-side component;

profiling the first network application, wherein a profile is generated based on monitored interactions between the client-side component and the server-side component; and

refactoring the first network application based on the profile.

24. The computer-implemented method of claim 23, wherein monitoring the first network application comprises mapping each of a plurality of incoming server-side requests generated by the client-side component to a corresponding server-side response generated by the server-side component.