Method, apparatus, and system for implementing a framework to support a web-based application

• US 6,901,595 B2
• Filed: 09/29/2001
• Issued: 05/31/2005
• 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, Ambrose, Jesse
• Primary Examiner(s): COURTENAY III, ST JOHN
• Application Number:
  US09/969,856
• Publication Number:
  US 20030070004A1
• Time in Patent Office: 1,340 Days
• Field of Search: 719310-320, 719/330, 717/116
• US Class Current: 719/316
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

According to one aspect of the present invention, a system is provided to support a web-based application. The system comprising a set of server-side objects managed by an object manager (OM), the set of server-side objects including a global session object providing access to a repository, a server-side business object, and server-side business components contained in the server-side business object. The system further comprises a set of browser-side objects running on a browser, the set of browser-side objects including a browser-side application object that exists throughout a user-session to manage other browser-side objects. The system also comprises a remote procedure call (RPC) mechanism and a notification mechanism to facilitate communication and synchronization between the browser-side objects and the server-side objects.

Claims

1. A system, comprising:

a set of server-side objects managed by an object manager (OM), the set of server-side objects including a global session object providing access to a repository, a server-side business object, and server-side business components contained in the server-side business object;

a set of browser-side objects running on a browser, the set of browser-side objects including a browser-side application object that exists throughout a user-session to manage other browser-side objects; and

a remote procedure call (RPC) mechanism to allow a single program to be divided between at least one server and at least one client; and

a notification mechanism to facilitate communication and synchronization between the browser-side objects and the server-side objects.

2. The system of claim 1, wherein the browser-side application object is loaded on the browser the user starts an application by invoking a subset of the application on from an icon or from a menu.

3. The system of claim 1, wherein:

the set of browser-side objects further includes a browser-side view object representing a collection of app lets; and

the set of server-side objects further includes a server-side view object corresponding to the browser-side view object.

4. The system of claim 1, wherein:

the set of browser-side objects further includes a browser-side business object to manage various one-to-many relationships between active business components; and

the set of server-side objects further includes a server-side business object corresponding the browser-side business object.

5. The system of claim 1, wherein:

the set of browser-side objects further includes at least one browser-side business component object representing at least one business component; and

the set of server-side objects further includes at least one server-side business component object corresponding to the at least one browser-side business component.

6. The system of claim 1, wherein the set of browser-side objects and the set of server-side objects are configured to reside and operate on a single computing device.

7. The system of claim 1, wherein the set of browser-side objects and the set of server-side objects are configured to reside and operate on multiple computing devices.

8. A method, comprising:

generating an invoke method corresponding to input from the user;

processing the invoke method at a browser-side applet;

generating a remote procedure call using a browser-side application object to retarget the invoke method to a server-side applet corresponding to the browser-side applet;

processing the generated remote procedure call at the server-side applet and returning a status flag from the server-side applet; and

examining and responding to the returned status flag at the browser-side applet.

9. The method of claim 8, further comprising:

loading the browser-side application object when the user starts an application by invoking a subset of the application.

10. The method of claim 8, further comprising:

retaining the browser-side application object throughout a user-session.

11. The method of claim 8, further comprising:

redirecting the invoke method from the browser-side applet to a browser-side business component object.

12. The method of claim 11, further comprising:

processing the invoke method at the browser-side business component object.

13. The method of claim 11, further comprising:

redirecting the invoke method from the browser-side business component object to a server-side business component object;

processing the invoke method at the server-side business component object; and

returning the status flag from the server-side business component object.

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

generating an invoke method corresponding to input from the user;

processing the invoke method at a browser-side applet;

generating a remote procedure call using a browser-side application object to retarget the invoke method to a server-side applet corresponding to the browser-side applet;

processing the generated remote procedure call at the server-side applet and returning a status flag from the server-side applet; and

examining and responding to the returned status flag at the browser-side applet.

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

loading the browser-side application object when the user starts an application by invoking a subset of the application.

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

retaining the browser-side application object throughout a user-session.

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

redirecting the invoke method from the browser-side applet to a browser-side business component object.

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

processing the invoke method at the browser-side business component object.

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

redirecting the invoke method from the browser-side business component object to a server-side business component object.

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

processing the invoke method at the server-side business component object; and

returning the status flag from the server-side business component object.