Method and system for a remote notification service for a multi-user server architecture

• US 5,920,692 A
• Filed: 03/24/1997
• Issued: 07/06/1999
• Est. Priority Date: 03/24/1997
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Singhal, Sandeep Kishan, Redpath, Richard J., Nguyen, Binh Q.
• Primary Examiner(s): Asta, Frank J.
• Assistant Examiner(s): YUAN, ALMARI ROMERO
• Application Number:
  US08/823,272
• Time in Patent Office: 834 Days
• Field of Search: 395/200.3, 395/200.49, 395/200.8, 395/200.58, 395/200.6, 395/703, 395/800.28, 395/800.29, 395/200.34, 395/200.35, 395/200.54, 463/42
• US Class Current: 709/204
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

An optimized design for a multi-user server architecture for disseminating a variety of real-time application data, such as audio, video, text and motion, while supporting general purpose tools. A general server system without an imposed GUI enables the end purchaser to customize the user interface as well as execute tools to monitor and control the operation of the system.

Claims

1. A method of providing a remote notification service compatible with a plurality of listener interface types, comprising the steps of:

requesting registration of a listener having an associated one of the plurality of listener interface types and having an interest in notification of at least one event by requesting registration from a notification directory;

receiving at the notification directory the registration request of the listener;

associating the listener with a corresponding notifier object associated with the listener interface type of the listener so as to register the listener with the corresponding notifier object;

distributing notification of events having associated listener interface types to notifier objects corresponding to the listener interface types associated with the events; and

wherein the notifier object provides notification of events to registered listeners utilizing the listener interface associated with the notifier object.

2. The method of claim 1, wherein said step of requesting registration further comprises:

providing a listener object to the notification directory containing at least one listener as a desired recipient of notification of said at least one event, wherein the listener object utilizes the associated one of the plurality of listener interface types.

3. The method of claim 2, further comprising:

receiving notification of said at least one event at said listener object.

4. The method of claim 1, further comprising the step of:

providing command objects for controlling a server to listeners registered with the notification directory so as to allow listeners registered with the notification directory to initiate commands on the server.

5. The method of claim 4, further comprising the steps of:

registering the notification directory with an object request broker so as to allow listeners to locate command objects;

locating a command object associated with the notification directory utilizing the object request broker; and

initiating a remote command through said command object so as to control the server.

6. A system for providing a remote notification service compatible with a plurality of listener interface types, comprising:

means for requesting registration of a listener having an associated one of the plurality of listener interface types and having an interest in notification of at least one event by requesting registration from a notification directory;

means for receiving at the notification directory the registration request of the listener;

means for associating the listener with a corresponding notifier object associated with the listener interface type of the listener so as to register the listener with the corresponding notifier object;

means for distributing notification of events having associated listener interface types to notifier objects corresponding to the listener interface types associated with the events; and

wherein the notifier object provides notification of events to registered listeners utilizing the listener interface associated with the notifier object.

7. The system of claim 6, wherein said means for requesting registration further comprises:

means for providing a listener object to the notification directory containing at least one listener as a desired recipient of notification of said at least one event, wherein the listener object utilizes the associated one of the plurality of listener interface types.

8. The system of claim 7, further comprising:

means for receiving notification of said at least one event at said listener object.

9. The system of claim 6, further comprising:

means for providing command objects for controlling a server to listeners registered with the notification directory so as to allow listeners registered with the notification directory to initiate commands on the server.

10. The system of claim 9, further comprising:

means for registering the notification directory with an object request broker so as to allow listeners to locate command objects;

means for locating a command object associated with the notification directory utilizing the object request broker; and

means for initiating a remote command through said command object so as to control the server.

11. A computer program product recorded on computer readable medium for providing a remote notification service compatible with plurality of listener interface types, comprising:

computer readable means for requesting registration of a listener having an associated one of the plurality of listener interface types and having an interest in notification of at least one event by requesting registration from a notification directory;

means for receiving at the notification directory the registration request of the listener;

computer readable means for associating the listener with a corresponding notifier object associated with the listener interface type of the listener so as to register the listener with the corresponding notifier object;

computer readable means for distributing notification of events having associated listener interface types to notifier objects corresponding to the listener interface types associated with the events; and

wherein the notifier object provides notification of events to registered listeners utilizing the listener interface associated with the notifier object.

12. The program product of claim 11, wherein said computer readable means for requesting registration further comprises:

computer readable means for providing a listener object to the notification directory containing at least one listener as a desired recipient of notification of said at least one event, wherein the listener object utilizes the associated one of the plurality of listener interface types.

13. The program product of claim 12, further comprising:

computer readable means for receiving notification of said at least one event at said listener object.

14. The program product of claim 11, further comprising:

computer readable means for providing command objects for controlling a server to listeners registered with the notification directory so as to allow listeners registered with the notification directory to initiate commands on the server.

15. The program product of claim 11, further comprising:

computer readable means for registering the notification directory with an object request broker so as to allow listeners to locate command objects;

computer readable means for locating a command object associated with the notification directory utilizing the object request broker; and

computer readable means for initiating a remote command through said command object so as to control the server.