Method, apparatus, and system for implementing caching of view custom options in a framework to support web-based applications

• US 7,603,677 B2
• Filed: 04/10/2007
• Issued: 10/13/2009
• Est. Priority Date: 09/29/2001
• Status: Expired due to Term

• Current Assignee: Siebel Systems Inc. (Oracle Corporation)
• Original Assignee: Siebel Systems Inc. (Oracle Corporation)
• Inventors: Coppens, William E., Mukundan, Anil, Coker, John
• Primary Examiner(s): Nguyen; Van H
• Application Number:
  US11/786,068
• Publication Number:
  US 20070199006A1
• Time in Patent Office: 917 Days
• Field of Search: 719/310, 719/316, 719/318, 719/330, 709/203, 709/219, 709/217, 709/218, 707/2, 707/3, 707/10, 717/116, 715/500.1
• US Class Current: 719/330
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]

Abstract

In one implementation, a system caches view custom options in a framework to support web-based applications. A set of server-side objects is managed by an object manager (OM) running on a server. A set of browser-side objects runs on a browser running on a client. A remote procedure call (RPC) mechanism enables re-targeting of methods from browser-side objects to server-side objects. A notification mechanism facilitates transmission of notifications from server-side objects to browser-side objects. A cache on the client stores custom options of views.

Claims

1. A system comprising:

at least one processor;

a plurality of server-side objects, wherein

said server-side objects are configured to be executed on a server;

an object manager (OM), wherein

said OM is configured to be executed on said server, and

said OM is configured to manage said server-side objects;

a remote procedure call (RPC) mechanism, wherein

said RPC mechanism is configured to re-target a method from at least one of a plurality of browser-side objects to at least one of said server-side objects, in response to said method being unhandled after being directed to said at least one browser-side object, and

said browser-side objects are configured to be executed on a browser configured to be executed on a client;

a notification mechanism, wherein

said notification mechanism is configured to facilitate communication of a notification from said at least one of said server-side objects to said at least one of said browser-side objects; and

a cache, wherein

said cache is maintained on said client,

said cache is configured to store a plurality of custom options of a view, and

said view is a display panel comprising a particular arrangement of applets.

2. The system of claim 1, wherein said client is configured to

receive a request to switch to said view,

retrieve custom options of said view from said server, and

store said custom options of said view in said cache, if said custom options of said view have not been cached.

3. The system of claim 2, wherein said client is configured to use said RPC mechanism and said notification mechanism to retrieve said custom options of said view from said server.

4. The system of claim 2, wherein said client is configured to

create and display said view using said custom options retrieved from said server,

retrieve data for said view from said server, and

populate said view with said data retrieved from said server.

5. The system of claim 2, wherein said client is configured to retrieve said custom options of said view from said cache, if said custom options of said view have been cached.

6. The system of claim 1, wherein said RPC mechanism comprises:

a client RPC stub configured to marshal input arguments and unmarshal output arguments; and

a server RPC stub configured to unmarshal input arguments and marshal output arguments.

7. The system of claim 1, wherein said method being unhandled after being directed to said at least one browser-side object comprises:

said method being unhandled after being redirected to said at least one browser-side object.

8. A method, comprising:

loading an object manager (OM) on a server;

loading a plurality of server-side objects on said server, wherein

said server-side objects are managed by said OM;

re-targeting a method from at least one of a plurality of browser-side objects to at least one of said server-side objects using a remote procedure call (RPC) mechanism, wherein

said browser-side objects are configured to be executed on a browser configured to be executed on a client, and

said re-targeting is performed in response to said method being unhandled after being directed to said at least one browser-side object;

facilitating communication of notifications from said server-side objects to said browser-side objects using a notification mechanism; and

providing a cache on said client to store custom options of views, wherein each view is a display panel comprising a particular arrangement of applets.

9. The method of claim 8, further comprising:

receiving a request from a user to switch to a view;

retrieving custom options of said view from said server if said custom options of said view have not been cached; and

saving said custom options of said view in said cache, if said custom options of said view have not been cached.

10. The method of claim 9, further comprising:

retrieving said custom options of said view from said server using said RPC mechanism and said notification mechanism.

11. The method of claim 9, further comprising:

creating and displaying said view using said custom options retrieved from said server,

retrieving data for said view from said server, and

populating said view with said data retrieved from said server.

12. The method of claim 8, further comprising:

retrieving said custom options of said view from said cache, if said custom options of said view have been saved in said cache.

13. The method of claim 12, further comprising:

creating and displaying said view using said custom options retrieved from said cache,

retrieving data for said view from said server, and

populating said view with said data retrieved from said server.

14. A computer program product comprising:

a first set of instructions, executable on a computer system, configured to load an object manager (OM) on a server;

a second set of instructions, executable on said computer system, configured to load a plurality of server-side objects on said server, wherein

said server-side objects are managed by said OM;

a third set of instructions, executable on said computer system, configured to re-target a method, from at least one of a plurality of browser-side objects to at least one of said server-side objects, in response to said method being unhandled after being directed to said at least one browser-side object, using a remote procedure call (RPC) mechanism, wherein

said browser-side objects are configured to be executed on a browser configured to be executed on a client; and

a fourth set of instructions, executable on said computer system, configured to facilitate communication of notifications from said server-side objects to said browser-side objects using a notification mechanism;

a fifth set of instructions, executable on said computer system, configured to access a cache on said client to store custom options of views, wherein each view is a display panel comprising a particular arrangement of applets; and

computer readable storage media, wherein said computer program product is encoded in said computer readable storage media.

15. The computer program product of claim 14, further comprising:

a sixth set of instructions, executable on said computer system, configured to receive a request from a user to switch to a view;

a seventh set of instructions, executable an said computer system, configured to retrieve custom options of said view from said server if said custom options of said view have not been cached; and

an eighth set of instructions, executable on said computer system, configured to save said custom options of said view in said cache, if said custom options of said view have not been cached.

16. The computer program product of claim 15, further comprising:

a ninth set of instructions, executable on said computer system, configured to retrieve said custom options of said view from said server using said RPC mechanism and said notification mechanism.

17. The computer program product of claim 15, further comprising:

a ninth set of instructions, executable on said computer system, configured to create and display said view using said custom options retrieved from said server;

a tenth set of instructions, executable on said computer system, configured to retrieve data for said view from said server; and

a eleventh set of instructions, executable on said computer system, configured to populate said view with said data retrieved from said server.

18. The computer program product of claim 14, further comprising:

a sixth set of instructions, executable on said computer system, configured to retrieve said custom options of said view from said cache, if said custom options of said view have been saved in said cache.

19. The computer program product of claim 18, further comprising:

a seventh set of instructions, executable on said computer system, configured to create and display said view using said custom options retrieved from said cache; and

an eighth set of instructions, executable on said computer system, configured to retrieve data for said view from said server; and

a ninth set of instructions, executable on said computer system, configured to populate said view with said data retrieved from said server.