METHOD AND SYSTEM FOR DISPLAYING HTTP SESSION ENTRY AND EXIT POINTS

• US 20090064088A1
• Filed: 08/28/2007
• Published: 03/05/2009
• Est. Priority Date: 08/28/2007
• Status: Active Grant

• Current Assignee: Proactive Patents
• Original Assignee: International Business Machines Corporation
• Inventors: Peterson, Robert Ross, Bhogal, Kulvir Singh, Barcia, Roland
• Granted Patent: US 8,607,197 B2
• Time in Patent Office: Days
• US Class Current: 717/102
• CPC Class Codes: G06F 11/3604 Software analysis for verifying properties of programs byte-code verification G06F9/44589
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 8/75 Structural analysis for program understanding

Abstract

A monitoring tool continuously monitors for insertion, call or deletion of objects from a session. Display of this information shows any get object, set object or remove object operations in the session and shows the entry and exit points for each such object, thus assisting the user whenever objects inserted or called remain in the session and are not removed, thus allowing the user to prevent any data buildup in the session.

Claims

1. An enhanced IDE system having an object entry point, exit point and read point analysis facility comprising:

means for inspecting newly written code for a session to identify any interactions with the session where object entry, exit or read points occur,

means for storing any such points in a data file,

means for comparing the content of the session code with said data file and

means for removing any point from said data file when said comparison finds that said point has been removed from said session.

means for displaying the identity of any such points as remain in said data file.

2. The enhanced IDE system of claim 1, further comprising:

means for displaying the identity of any instruction creating such points as remain in said data file.

3. The enhanced IDE system of claim 1 or claim 2, further comprising:

means for displaying said entry, exit or read points in said session in association with the identity of the particular instruction which caused such entry, exit or read point to be created.

4. A method of identifying any inserted and unremoved objects in the source code of a session under development comprising steps of:

inspecting said code for any new session access instruction that either enters, reads or removes an object,

storing the entry, exit or read point of said access instruction in a data file,

comparing the content of said data file with the content of said code to determine which of said entry, exit or read points remains in said data file but not in said code, and

displaying the entry, exit or read point of an object stored in said data file.

5. The method of claim 4, further comprising a step of:

removing from said data file any stored entry, exit or read point of an object which is found by said comparison step not to be present in said code when said comparison is made.

6. The method of claim 4, wherein said displaying step further comprises:

displaying the identity of any session interaction instruction creating an entry, exit or read point in conjunction with each said entry, exit or read point remaining in said data file.

7. The method of claim 4 or 5 or 6 further comprising a step of:

highlighting in said displaying step the identity of any said entry, exit or read point from said data file.

8. A program product for analyzing source code to identify any inserted but unremoved objects comprising machine executable instructions for:

inspecting said code for any new session interaction instruction that either enters, reads or removes an object,

storing the entry, exit or read point of said access instruction in a data file,

comparing the content of said data file with the content of said code to determine which of said entry, exit or read points remains in said data file but not in said code, and

displaying the entry, exit or read point of an object stored in said data file

9. A program product as described in claim 8, further comprising machine executable instructions for:

removing from said data file any stored entry, exit or read point of an object which is found by said comparison step not to be present in said code when said comparison is made.

10. A program product as described in claim 8 or claim 9, further comprising machine readable instructions for:

displaying the identity of any session interaction instruction causing an entry, exit or read point in said session in conjunction with each said entry, exit or read point remaining in said data file.

11. A program product as described in claim 8 or claim 9 or claim 10, further comprising machine executable instructions for:

highlighting in said displaying step the identity of any said entry, exit or read point from said data file.

12. A monitoring tool for detecting interactions with a session that create entry, exit or read points therein comprising:

means for inspecting newly written code for a session to identify any interactions with the session where object entry, exit or read points occur,

means for storing any such points in a data file,

means for comparing the content of the session code with said data file and

means for removing any point from said data file when said comparison finds that said point has been removed from said session.

means for displaying the identity of any such points as remain in said data file.

13. A monitoring tool as described in claim 12, further comprising:

means for displaying the identity of any instruction creating such points as remain in said data file.

14. A monitoring tool as described in claim 12 or claim 13, further comprising:

means for displaying said entry, exit or read points in said session in association with the identity of the particular instruction which caused such entry, exit or read point to be created.