Shared listeners in shared object space

• US 7,689,986 B2
• Filed: 10/21/2003
• Issued: 03/30/2010
• Est. Priority Date: 10/21/2003
• Status: Active Grant

• Current Assignee: Pivotal Software, Inc. (Broadcom, Inc.)
• Original Assignee: GemStone Systems, Inc. (Broadcom, Inc.)
• Inventors: Bretl, Robert, Monnie, David J.
• Primary Examiner(s): An; Meng-Ai
• Assistant Examiner(s): Kawsar; Abdullah Al
• Application Number:
  US10/690,793
• Publication Number:
  US 20050097567A1
• Time in Patent Office: 2,352 Days
• Field of Search: 718 1-108, 709201-219, 711/100, 711/147, 711/148, 711/153
• US Class Current: 718/1
• CPC Class Codes: G06F 2209/543 Local
• CPC Class Codes: G06F 9/52 Program synchronisation; Mutual exclusion, e.g. by means of semaphores
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes

Abstract

A system for sharing listeners monitoring events occurring in objects shared by multiple applications each running inside its own virtual machine in a computer system.

Claims

1. A computer system for concurrent operation of plural applications, said computer system comprising:

(a) a memory including a shared object space capable of storing at least one shared object and a listener;

(b) a shared object stored in said shared object space and accessible to at least two applications so that at least a first application is capable of causing an event in said shared object, said first application running in a first virtual machine;

(c) a listener attached to said shared object and operably associated with a second application running in a second virtual machine, said listener listening for said event and notifying said second application when said first application has caused said event; and

(d) said listener being able to identify an application other than said second application as causing said event.

2. The system of claim 1 where said listener is located in said shared object space.

3. The system of claim 1 where at least two applications are capable of causing said event.

4. The system of claim 1 further comprising a second listener located in said shared object space and attached to said shared object.

5. The system of claim 1 where at least one of said virtual machines is a Java virtual machine.

6. The system of claim 1 where said shared object space is linked to at least one application by a native method interface enabling said application to utilize a method native to said application in interacting with said shared object.

7. The system of claim 6 where said system includes a default directory with a native library.

8. The system of claim 1 including a non-object-oriented application.

9. The system of claim 8 where said non-object-oriented application is a C application.

10. The system of claim 1 where access to said at least one object by said plural applications is synchronized.

11. The system of claim 1 where said plural applications implement a stock trading system.

12. The system of claim 1 where said at least one object is copy shared among said plural applications.

13. The system of claim 1 where said at least one object is direct shared among said plural applications.

14. The system of claim 1 including a system manager that analyzes information pertaining to the operation of said shared object space.

15. The system of claim 1 including a global name space in said shared object space.

16. A computer system for concurrent operation of plural applications, said computer system comprising:

(a) a memory including a shared object space capable of storing at least one shared object and a listener;

(b) a shared object stored in said shared object space and accessible to at least two applications so that at least one application is capable of causing an event in said shared object, said application running in a virtual machine and said shared object containing a header capable of containing an identifier of the application that caused said event;

(c) a listener attached to said shared object and operably associated with at least one application running in a virtual machine, said listener listening for said event and notifying an associated application not causing said event of an occurrence of said event; and

(d) said listener being able to identify from said header an application other than said associated application as an application causing said event.

17. The system of claim 16 where said listener is located in said shared object space.

18. The system of claim 16 where at least two applications are capable of causing said event.

19. The system of claim 16 further comprising a second listener located in said shared object space and attached to said shared object.

20. The system of claim 16 where at least one of said virtual machines is a Java virtual machine.

21. The system of claim 16 where said shared object space is linked to at least one application by a native method interface enabling said application to utilize a method native to said application in interacting with said shared object.

22. The system of claim 21 where said system includes a default directory with a native library.

23. The system of claim 16 including a non-object-oriented application.

24. The system of claim 23 where said non-object-oriented application is a C application.

25. The system of claim 16 where access to said at least one object by said plural applications is synchronized.

26. The system of claim 16 where said plural applications implement a stock trading system.

27. The system of claim 16 where said at least one object is copy shared among said plural applications.

28. The system of claim 16 where said at least one object is direct shared among said plural applications.

29. The system of claim 16 including a system manager that analyzes information pertaining to the operation of said shared object space.

30. The system of claim 16 including a global name space in said shared object space.