JSP composition in a cache for web applications with dynamic content

• US 20020111992A1
• Filed: 12/18/2000
• Published: 08/15/2002
• Est. Priority Date: 12/18/2000
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Copeland, George P., Flurry, Gregory A., Conner, Michael H.
• Application Number:
  US09/740,460
• Publication Number:
  US 20020111992A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system and method are disclosed, according to which performance of client/server-based distributed web applications operating in an object-oriented environment may be improved, by increasing the capacity of a cache for Java Server Pages (JSPs). The main body of a JSP may contain calls to several other JSPs. The conventional method of caching such a composite JSP places a fully expanded version of each called JSP at the point in the main code from which it is called. This can result in considerable redundancy, since the same JSP may be called from several places. In an exemplary embodiment of the techniques disclosed herein for caching composite JSPs, the called JSPs are stored separately from the main JSP, along with links allowing the called JSPs to be located in the cache or executed. This eliminates redundancy, since only one copy of each called JSP is required.

Claims

1. A software system supporting distributed web applications, comprising:

a parent server page, containing a call to a child server page;

a cache, containing code for the parent server page and child server page, wherein the code for the parent server page does not contain all the code for the child server page; and

a link associated with the call to the child server page, and encapsulating information for locating and executing the code for the child server page.

2. The software system as recited in claim 1, wherein the child server page may be executed using the link, without executing the parent server page.

3. The software system as recited in claim 1, wherein the link further comprises a web page address and a list of request attributes.

4. The software system as recited in claim 1, wherein the cache is associated with a web server.

5. The software system as recited in claim 1, further comprising an instruction sequence that may be invoked to locate the child server page in the cache.

6. The software system as recited in claim 1, further comprising an object-oriented software system.

7. The software system as recited in claim 1, wherein a server page comprises a Java Server Page (JSP).

8. The software system as recited in claim 7, wherein the child JSP may be executed in response to a request made to the web server by the client or another web server.

9. A method for caching a parent and a child sever page, comprising:

storing code for the parent sever page in a cache, such that the code for the parent sever page does not contain all lines of code for the child sever page;

storing only one copy of the code for the child sever page in the cache;

creating in the code for the parent sever page a link to the singular copy of the code for the child sever page for locating and executing the code for the child sever page; and

associating the link with more than one call to the child sever page to execute from the cache a plurality of the singular copy of the code for the child sever page.

10. The method as recited in claim 9, wherein a server page comprises a Java Server Page (JSP).

11. The method as recited in claim 10, further comprising invoking an instruction sequence to locate the code for the child JSP in the cache, in response to a request made by a web browser.

12. The method as recited in claim 10, further comprising executing the code for the child JSP using the link, without executing all the code for the parent JSP.

13. The method as recited in claim 12, wherein the child JSP is executed in the web server in response to a request made by the client or another web server.

14. The method as recited in claim 13, wherein the child JSP is executed only if it cannot first be located in the cache.

15. The method as recited in claim 13, wherein the cached child JSP may be updated without also updating the parent JSP.

16. A computer product, comprising a web server and a software system, wherein the web server includes a processor, memory, mass storage and a network interface, and the software system is adapted for caching a parent and a child sever page, such that the code for the parent sever page does not contain all lines of code for the child sever page.

17. A computer program product in a computer readable medium for use in storing a parent and a child server page in a cache, the computer program product comprising:

instructions for storing code for the parent sever page in the cache, such that the code for the parent sever page does not contain all lines of code for the child sever page;

instructions for storing only one copy of the code for the child sever page in the cache;

instructions for creating in the code for the parent sever page a link to the singular copy of the code for the child sever page for locating and executing the code for the child sever page; and

instructions for associating the link with more than one call to the child sever page to execute from the cache a plurality of the singular copy of the code for the child sever page.

18. A server including memory and processor comprising;

means for storing code for the parent sever page in the cache, such that the code for the parent sever page does not contain all lines of code for the child sever page;

means for storing only one copy of the code for the child sever page in the cache;

means for creating in the code for the parent sever page a link to the singular copy of the code for the child sever page for locating and executing the code for the child sever page; and

means for associating the link with more than one call to the child sever page to execute from the cache a plurality of the singular copy of the code for the child sever page.