METHOD, APPARATUS, AND SYSTEM FOR IMPLEMENTING CACHING OF VIEW CUSTOM OPTIONS IN A FRAMEWORK TO SUPPORT WEB-BASED APPLICATIONS

• US 20070016915A1
• Filed: 09/29/2001
• Published: 01/18/2007
• Est. Priority Date: 09/29/2001
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Siebel Systems Inc. (Oracle Corporation)
• Inventors: Mukundan, Anil, Coker, John, Coppens, William
• Granted Patent: US 7,203,948 B2
• Time in Patent Office: Days
• 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

According to one aspect of the present invention, a system is provided for implementing caching of view custom options in a framework to support web-based applications. The system comprising a set of server-side objects managed by an object manager (OM) running on a server. The system further comprises a set of browser-side objects running on a browser running on a client. The system also comprises a remote procedure call (RPC) mechanism to enable re-targeting of methods from browser-side objects to server-side objects. The system additionally comprises a notification mechanism to facilitate transmission of notifications from server-side objects to browser-side objects. The system also comprises a cache on the client to store custom options of views, wherein each view is a display panel consisting of a particular arrangement of applets.

Claims

1. A system, comprising:

a set of browser-side objects running on a browser running on a client;

a remote procedure call (RPC) mechanism to enable re-targeting of methods from browser-side objects to a set of server-side objects managed by an object manager (OM) running on a server;

a notification mechanism to facilitate transmission of notifications from server-side objects to browser-side objects; and

a cache on the client to store custom options of views;

wherein the client is to receive a request from a user to switch to a view, and to retrieve custom options of the view from the server using the RPC mechanism and the notification mechanism and to store the custom options of the view in the cache if the custom options of the view have not been cached.

2. The system of claim 1, wherein each view is a display panel consisting of a particular arrangement of applets.

4. The system of claim 2, wherein the client flushes the cache, if the cache is full, to clear up storage space in the cache for the custom options of the view.

5. The system of claim 2, wherein the client creates and displays the view using the custom options retrieved from the server, retrieves data for the view from the server, and populates the view with the retrieved data.

6. The system of claim 1, wherein the client retrieves the custom options of the view from the cache, if the custom options of the view have been cached, to save a round trip to the server.

7. The system of claim 6, wherein the client creates and displays the view using the custom options retrieved from the cache, retrieves data for the view from the server, and populates the view with the data retrieved from the server.

22. The system of claim 2, wherein the applets are represented by browser-side objects capable of receiving notification from server-side objects using the notification mechanism and having methods that are capable of being re-targeted to server-side objects using the remote procedure call (RPC) mechanism.

3. (canceled)

8. A method, comprising:

loading a set of browser-side objects on a browser running on a client;

enabling re-targeting of methods from browser-side objects to a set of server-side objects managed by an object manager (OM) running on a server using a remote procedure call (RPC) mechanism;

facilitating transmission of notifications from the server-side objects to browser-side objects using a notification mechanism;

providing a cache on the client to store custom options of views;

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

retrieving custom options of the view from the server using the RPC mechanism and the notification mechanism if the custom options of the view have not been cached; and

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

9. The method of claim 8, wherein each view is a display panel consisting of a particular arrangement of applets.

11. The method of claim 9, further comprising:

flushing the cache, if the cache is full, to clear up storage space in the cache for the custom options of the view.

12. The method of claim 9, further comprising:

creating and displaying the view using the custom options retrieved from the server;

retrieving data for the view from the server; and

populating the view with the data retrieved from the server.

13. The method of claim 8, further comprising:

retrieving the custom options of the view from the cache, if the custom options of the view have been saved in the cache, to save a round trip to the server.

14. The method of claim 13, further comprising:

creating and displaying the view using the custom options retrieved from the cache;

retrieving data for the view from the server; and

populating the view with the data retrieved from the server.

10. (canceled)

15. A machine-readable medium comprising instructions which, when executed by a machine, cause the machine to perform operations comprising:

loading a set of browser-side objects on a browser running on a client;

enabling re-targeting of methods from browser-side objects to a set of server-side objects managed by an object manager (OM) running on a server using a remote procedure call (RPC) mechanism;

facilitating transmission of notifications from the server-side objects to browser-side objects using a notification mechanism;

providing a cache on the client to store custom options of views;

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

retrieving custom options of the view from the server using the RPC mechanism and the notification mechanism if the custom options of the view have not been cached; and

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

16. The machine-readable medium of claim 15, wherein each view is a display panel consisting of a particular arrangement of applets.

18. The machine-readable medium of claim 16, further comprising:

flushing the cache, if the cache is full, to clear up storage space in the cache for the custom options of the view.

19. The machine-readable medium of claim 15, further comprising:

creating and displaying the view;

retrieving data for the view from the server;

populating the view with the data retrieved from the server; and

applying to the view the custom options retrieved from the server.

20. The machine-readable medium of claim 15, further comprising:

retrieving the custom options of the view from the cache, if the custom options of the view have been cached, to save a round trip to the server.

21. The machine-readable medium of claim 20, further comprising:

creating and displaying the view;

retrieving data for the view from the server;

populating the view with the data retrieved from the server; and

applying to the view the custom options retrieved from the cache.

17. (canceled)