Method for provisioning distributed web applications

• US 20040024843A1
• Filed: 07/31/2002
• Published: 02/05/2004
• Est. Priority Date: 07/31/2002
• Status: Abandoned Application

• Current Assignee: Tripwire Incorporated (Belden Inc.)
• Original Assignee: ORIX Growth Capital, LLC (ORIX Corporation)
• Inventors: Smith, Christopher T.
• Application Number:
  US10/209,818
• Publication Number:
  US 20040024843A1
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces

Abstract

A method and apparatus for provisioning distributed web applications includes a server receiving an identifier corresponding to a first user interface (UI) object to be displayed within a client browser, the server generating one or more client-side scripts designed to facilitate generation of a hierarchical client based object model, the hierarchical object model including a root object, a context object to store state information corresponding to at least one of the root object and one or more child objects, and a window manager to facilitate control of one or more display properties of at least one secondary UI window, the server delivering content and the one or more client-side scripts to the client, and the client generating hierarchical client based object model in response to the execution of the one or more client-side scripts.

Claims

1. In a server, a method comprising:

receiving an identifier corresponding to a first user interface (UI) object to be displayed within a client browser;

generating one or more client-side scripts designed to facilitate generation of a hierarchical client based object model, the hierarchical object model including a root object, a context object to store state information corresponding to at least one of the root object and one or more child objects, and a window manager to facilitate control of one or more display properties of at least one secondary UI window;

generating display content associated with the first user interface object; and

transmitting the one or more client-side scripts, and content representing at least the first UI object.

2. The method of claim 1, wherein the first UI object comprises an outputDisplay method to facilitate generation of the display content, and an outputScript method to facilitate generation the one or more client-side scripts.

3. The method of claim 1, wherein the one or more client-side scripts are generated based upon meta-data stored within a corresponding hierarchically arranged server-side model containing a root node and one or more child nodes.

4. The method of claim 3, wherein each node of the hierarchically arranged server-side model is independently addressable.

5. The method of claim 4, wherein if a parent node of the hierarchically arranged server-side model is accessed, at least a subset of the one or more client side scripts are generated based upon meta-data corresponding to a parent node and each child node corresponding to the parent node.

6. The method of claim 5, wherein the first UI object comprises an outputDisplay method to facilitate generation of the display content, and an outputScript method to facilitate generation the one or more client-side scripts.

7. The method of claim 3, wherein the one or more client-side scripts are composed in JavaScript.

8. The method of claim 3, wherein a Java Server Page (JSP) generates the display content and transmits the display content to the client.

9. The method of claim 1, wherein the command context object comprises a plurality of methods including at least a set parameter method for setting values that may be shared between objects of the client based object model, and a get parameter method for retrieving the values that may be shared between the objects of the client based object model.

10. In a client browser, a method comprising:

receiving an user indication identifying a first user interface (UI) object to be displayed within the client browser;

transmitting an identifier corresponding to the first UI object;

receiving content representing at least the first UI object, and one or more client-side scripts designed to generate a hierarchical client based object model;

displaying the content representing at least the first UI object; and

generating the hierarchical object model on the client in response to execution of the one or more client-side scripts, the hierarchical object model including a root object, a context object to store state information corresponding to at least one of the root object and one or more child objects, and a window manager to facilitate control of one or more display properties of at least one secondary UI window.

11. The method of claim 10, wherein the identifier comprises a uniform resource locator (URL) associated with the first user interface object.

12. The method of claim 11, wherein the display content is generated based upon parameter data associated with the URL.

13. The method of claim 11, wherein the display content is displayed within a frame set including a hidden frame, the hidden frame to act as a command conduit for network based communication with a server.

14. The method of claim 10, wherein the hierarchical client based object model corresponds to a hierarchically arranged server-side model containing plurality of nodes including a root node and one or more child nodes.

15. The method of claim 14, wherein the identifier comprises a uniform resource locator (URL) associated with one of the plurality of nodes.

16. The method of claim 10, wherein the one or more client-side scripts are generated based upon meta-data stored within a corresponding hierarchically arranged server-side model.

17. The method of claim 10, wherein the window manager maintains a mapping between each secondary UI window object and a unique window identifier corresponding to each of the secondary UI window objects to facilitate a managed, multi-window display of content within the client browser.

18. The method of claim 17, wherein if an object makes a call to a secondary UI window object listed within the window manager mapping, the secondary UI window associated with the listed secondary UI window object is recalled.

19. The method of claim 10, wherein the context object comprises a plurality of methods including a setParameter method, a getParameter method, an updateContext method, an updateForm method, and an addChangeListener method.

20. The method of claim 19, wherein the setParameter method sets values to be shared between objects of the client based object model, and the getParameter method retrieves the shared values.

21. The method of claim 19, wherein the updateContext method stores current state information associated with a form and the updateForm method updates the form to reflect the state information stored within the context object.

22. The method of claim 19, wherein the addChangeListener method allows components to register callbacks to be invoked if a change occurs to the context object.

23. In a client browser, a method comprising:

receiving an user indication identifying a first user interface (UI) object to be displayed within the client browser;

transmitting an identifier corresponding to the first UI object;

receiving content representing at least the first UI object, and one or more client-side scripts designed to generate a hierarchical client based object model;

displaying the content representing at least the first UI object; and

generating the hierarchical object model on the client in response to execution of the one or more client-side scripts, the hierarchical object model including a root object, and a command context to store state information corresponding to at least one of the root object and one or more child objects.

24. The method of claim 23, wherein the hierarchical object model further comprises:

a window manager to maintain a mapping between one or more secondary UI window objects and a unique window identifier corresponding to each of the secondary UI window objects to facilitate a managed, multi-window display of content within the client browser.

25. The method of claim 23, wherein the hierarchical client based object model corresponds to a hierarchically arranged server-side model containing plurality of nodes including a root node and one or more child nodes.

26. The method of claim 25, wherein the identifier comprises a uniform resource locator (URL) associated with one of the plurality of nodes.

27. An apparatus comprising:

a storage medium having programming instructions stored therein, which when executed operate to

receive an identifier corresponding to a first user interface (UI) object to be displayed within a client browser,

generate one or more client-side scripts designed to facilitate generation of a hierarchical client based object model, the hierarchical object model including a root object, a context object to store state information corresponding to at least one of the root object and one or more child objects, and a window manager to facilitate control of one or more display properties of at least one secondary UI window,

generate display content associated with the first user interface object, and

transmit the one or more client-side scripts, and content representing at least the first UI object; and

at least one processor coupled with the storage medium to execute the programming instructions.

28. The apparatus of claim 27, wherein the first UI object comprises an outputDisplay method to facilitate generation of the display content, and an outputScript method to facilitate generation the one or more client-side scripts.

29. The apparatus of claim 27, wherein the one or more client-side scripts are generated based upon meta-data stored within a corresponding hierarchically arranged server-side model containing a root node and one or more child nodes.

30. The apparatus of claim 29, wherein each node of the hierarchically arranged server-side model is independently addressable.

31. The apparatus of claim 30, wherein if a parent node of the hierarchically arranged server-side model is accessed, at least a subset of the one or more client side scripts are generated based upon meta-data corresponding to a parent node and each child node corresponding to the parent node.

32. The apparatus of claim 31, wherein the first UI object comprises an outputDisplay method to facilitate generation of the display content, and an outputScript method to facilitate generation the one or more client-side scripts.

33. The apparatus of claim 29, wherein the one or more client-side scripts are composed in JavaScript.

34. The apparatus of claim 29, wherein a Java Server Page (JSP) generates the display content and transmits the display content to the client.

35. The apparatus of claim 27, wherein the command context object comprises a plurality of methods including at least a set parameter method for setting values that may be shared between objects of the client based object model, and a get parameter method for retrieving the values that may be shared between the objects of the client based object model.

36. An apparatus comprising:

a storage medium having programming instructions stored therein, which when executed operate to

receive an user indication identifying a first user interface (UI) object to be displayed within the client browser,

transmit an identifier corresponding to the first UI object,

receive content representing at least the first UI object, and one or more client-side scripts designed to generate a hierarchical client based object model,

display the content representing at least the first UI object, and

generate the hierarchical object model on the client in response to execution of the one or more client-side scripts, the hierarchical object model including a root object, a context object to store state information corresponding to at least one of the root object and one or more child objects, and a window manager to facilitate control of one or more display properties of at least one secondary UI window; and

at least one processor coupled with the storage medium to execute the programming instructions.

37. The apparatus of claim 36, wherein the identifier comprises a uniform resource locator (URL) associated with the first user interface object.

38. The apparatus of claim 37, wherein the display content is generated based upon parameter data associated with the URL.

39. The apparatus of claim 37, wherein the display content is displayed within a frame set including a hidden frame, the hidden frame to act as a command conduit for network based communication with a server.

40. The apparatus of claim 36, wherein the hierarchical client based object model corresponds to a hierarchically arranged server-side model containing plurality of nodes including a root node and one or more child nodes.

41. The apparatus of claim 40, wherein the identifier comprises a uniform resource locator (URL) associated with one of the plurality of nodes.

42. The apparatus of claim 36, wherein the one or more client-side scripts are generated based upon meta-data stored within a corresponding hierarchically arranged server-side model.

43. The apparatus of claim 36, wherein the window manager maintains a mapping between each secondary UI window object and a unique window identifier corresponding to each of the secondary UI window objects to facilitate a managed, multi-window display of content within the client browser.

44. The apparatus of claim 43, wherein if an object makes a call to a secondary UI window object listed within the window manager mapping, the secondary UI window associated with the listed secondary UI window object is recalled.

45. The apparatus of claim 36, wherein the context object comprises a plurality of methods including a setParameter method, a getParameter method, an updateContext method, an updateForm method, and an addChangeListener method.

46. The apparatus of claim 45, wherein the setParameter method sets values to be shared between objects of the client based object model, and the getParameter method retrieves the shared values.

47. The apparatus of claim 45, wherein the updateContext method stores current state information associated with a form and the updateForm method updates the form to reflect the state information stored within the context object.

48. The apparatus of claim 45, wherein the addChangeListener method allows components to register callbacks to be invoked if a change occurs to the context object.