Method and apparatus for managing Internet transactions

Abstract
The object-oriented approach used by the present invention provides the ability to develop and manage Internet transactions. Local applications can be accessed using any workstation connected to the Internet regardless of the workstation's configuration. Some or all of a Web page can be generated dynamically using input received in a returned page, generated at runtime, or retrieved from an external data source (e.g., database or electronic mail system). When the Web page definition is rendered, the information contained in template(s), declaration file(s), and object(s) are used to generate standard definitions. State information is maintained across transactions. Using state information, virtual applications, sessions, transactions, and pages can be implemented. Self-contained modules, or components, provide the ability to share implementations and create multi-content documents. Event objects can be used to assist in event handling management.
Description

BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 provides an example of a general purpose computer to be used with the present invention.



FIG. 2 provides a block-level diagram that illustrates components of the present invention.



FIG. 3A provides a block-level diagram for accession a corporate application on the World Wide Web (WWW) using the present invention.



FIG. 3B provides an example of Web pages generated by an Automobile Shopper's application accessed via the WWW using the present invention.



FIG. 4 provides a diagram of the object tree.



FIGS. 5A-5E provides an example of a process flow for handling a client request.



FIG. 6A provides an example of resources associated with a control.



FIG. 6B provides a block-level diagram associated with component processing.



FIG. 6C provides examples of a parent tree and two component or sub-trees.



FIG. 7A provides the object tree that is generated when the HTML in Table Four is parsed.



FIG. 7B provides an example of the object tree of FIG. 7A and an associated repetition controller and repetition template.



FIG. 7C provides an example of the object tree of FIG. 7B that has been modified using a repetition controller and template.



FIG. 8 illustrates a rendering process flow.



FIGS. 9A-9B illustrate event handling object diagrams.



FIG. 10 illustrates context objects.



FIGS. 11A-11B illustrate the push and pull modes of the present invention.


Claims
  • 1-30. (canceled)
  • 31. A method for maintaining state information in a web application, comprising: defining a property associated with said state information; andretaining said state information based at least in part on said property.
  • 32. A method as recited in claim 31, wherein said state information is associated with one or more objects associated with said web application.
  • 33. A method as recited in claim 31, further comprising accessing said state information based at least in part upon said property.
  • 34. A method as recited in claim 31, wherein said property includes a duration of said state information.
  • 35. A method as recited in claim 31, wherein said property includes a scope of said state information.
  • 36. A method as recited in claim 31, wherein said property includes a storage policy for said state information.
  • 37. (canceled)
  • 38. (canceled)
  • 39. (canceled)
  • 40. (canceled)
  • 41. (canceled)
  • 42. (canceled)
  • 43. (canceled)
  • 44. (canceled)
  • 45. (canceled)
  • 46. (canceled)
  • 47. (canceled)
  • 48. (canceled)
  • 49. (canceled)
  • 50. (canceled)
  • 51. (canceled)
  • 52. (canceled)
  • 53. (canceled)
  • 54. (canceled)
  • 55. (canceled)
  • 56. (canceled)
  • 57. (canceled)
  • 58. (canceled)
  • 59. (canceled)
  • 60. (canceled)
  • 61. (canceled)
  • 62. (canceled)
  • 63. (canceled)
  • 64. (canceled)
  • 65. (canceled)
  • 66. (canceled)
  • 67. (canceled)
  • 68. (canceled)
  • 69. (canceled)
  • 70. A system for accessing a remote application from a local site, comprising: a remote application executing at a remote site and configured to receive a request and determine a response to said request; anda software application executing at a local site configured to display a web page and submit a request to said remote application via a network;wherein at least one module of said remote application is configured to dynamically generate a web page definition as said response.
  • 71. A system as recited in claim 70, wherein said at least one module generates said response by making one or more modifications to a pre-defined definition of a web page.
  • 72. A system as recited in claim 71, wherein said one or more modifications reflect insertions of state information into said pre-defined definition of a web page.
  • 73. A system as recited in claim 72, wherein said state information includes data retrieved from an external data source.
  • 74. A system as recited in claim 72, wherein said state information exists for the duration of a single request.
  • 75. A system as recited in claim 72, wherein said state information is accessible to multiple requests.
  • 76. A system as recited in claim 70, wherein said response web page includes custom logic used in processing said response.
  • 77. A system as recited in claim 76, wherein said response web page includes one or more declarations and wherein one declaration of said one or more declarations binds said custom logic to said response web page at run time.
  • 78. A system as recited in claim 76, wherein said custom logic is executed when said response web page is generated.
  • 79. A system as recited in claim 76, wherein said custom logic is executed when said response web page is returned.
  • 80. A system as recited in claim 70, wherein at least one module of said remote application is configured to cause said response to be transmitted to said software application via said network for display at said local site.
  • 81. A system as recited in claim 70, wherein said at least one module comprises one or more objects having one or more methods and one or more properties to generate said response as a web page.
  • 82. (canceled)
  • 83. (canceled)
  • 84. (canceled)
  • 85. (canceled)
  • 86. (canceled)
  • 87. (canceled)
  • 88. A system for maintaining state information in a web application, comprising: a processor configured to: define a property associated with said state information; andretain said state information based at least in part on said property; anda memory coupled to the processor and configured to provide instructions to the processor.
  • 89. A computer program product for maintaining state information in a web application, the computer program product being embodied in a computer readable medium and comprising computer instructions for: defining a property associated with said state information; andretaining said state information based at least in part on said property.
Continuations (3)
Number Date Country
Parent 11327196 Jan 2006 US
Child 11496965 US
Parent 09842284 Apr 2001 US
Child 11327196 US
Parent 08532491 Sep 1995 US
Child 09842284 US