TECHNIQUES TO MANAGE REMOTE EVENTS

• US 20130151690A1
• Filed: 12/08/2011
• Published: 06/13/2013
• Est. Priority Date: 12/08/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Nandwani, Sharad, Shah, Roma, Balaji M., Vijay, Kamalakumar, Pradeep, Banerjee, Atanu, Singhal, Ashish Kumar, Sunku, Suresh
• Granted Patent: US 9,324,055 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 51/10 Multimedia information
• CPC Class Codes: H04L 51/52 for supporting social networking services
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Abstract

Techniques to manage remote events are described. An apparatus may comprise a processor circuit and a remote event application arranged for execution by the processor circuit. The remote event application may be operative to manage remote event notifications for a publisher entity and a subscriber entity. The remote event application may comprise, among other elements, an event monitor component operative to receive an external event notification message with a publisher entity event for the publisher entity. The event monitor component may select a custom event receiver component associated with the publisher entity from among multiple custom event receiver components, and send the external event notification message to the selected custom event receiver component. The custom event receiver component may implement custom business logic, such as code callouts designed for specific application programs or system programs. Other embodiments are described and claimed.

Claims

1. An apparatus, comprising:

a processor circuit; and

a remote event application operative on the processor circuit to manage remote event notifications for a publisher entity and a subscriber entity, the remote event application comprising;

an event monitor component operative to receive an external event notification message with a publisher entity event for the publisher entity, select a custom event receiver component associated with the publisher entity from among multiple custom event receiver components, and send the external event notification message to the selected custom event receiver component.

2. The apparatus of claim 1, the event monitor component comprising a representational state transfer (REST) based input point.

3. The apparatus of claim 1, the publisher entity comprising a data source for the external application.

4. The apparatus of claim 1, the publisher entity event comprising a change in state of data stored by a data source for the external application.

5. The apparatus of claim 1, the event monitor component operative to select the custom event receiver component for the external event notification message based on a globally unique identifier (GUID) for the publisher entity associated with the external event notification message.

6. The apparatus of claim 1, the custom event receiver component operative to receive the external event notification message, and invoke a code callout arranged to perform custom logic in response to the publisher entity event.

7. The apparatus of claim 1, the remote event application comprising an event notification component operative to retrieve a notification parameter associated with the subscriber entity, and send a client event notification message to a client application associated with the subscriber entity that subscribes to the publisher entity.

8. The apparatus of claim 1, the remote event component comprising an event management component operative to manage a subscription between the publisher entity and the subscriber entity.

9. The apparatus of claim 8, the event management component operative to manage a level of reliability for external event notification messages.

10. The apparatus of claim 8, the event management component operative to retrieve a reliability parameter representing a reliability level associated with the publisher entity, and process the external event notification message based on the reliability parameter.

11. The apparatus of claim 8, comprising a set of message handling parameters associated with a reliability parameter, the message handling parameters comprising a duplicate message parameter, a standby server parameter, or a replay parameter, the duplicate message parameter indicating whether to accept or reject duplicate external event notification messages received from the external application, the standby server parameter indicating whether to send the external event notification message to a standby server when a primary server is non-operational, and the replay parameter indicating whether to replay the external event notification message when the event monitor component detects an error condition when processing the external event notification message.

12. A computer-implemented method, comprising:

receiving an external event notification message with a publisher entity event for a publisher entity from a first server device by a second server device;

selecting a custom event receiver component associated with a publisher entity from among multiple custom event receiver components at the second server device;

sending the external event notification message to the selected custom event receiver component at the second server device; and

sending a client event notification message to a subscriber entity subscribed to the publisher entity from the second server device to a client device.

13. The computer-implemented method of claim 12, comprising selecting the custom event receiver component for the external event notification message based on a globally unique identifier (GUID) for the publisher entity associated with the external event notification message.

14. The computer-implemented method of claim 12, comprising invoking a code callout arranged to perform custom logic in response to the publisher entity event.

15. The computer-implemented method of claim 12, comprising sending the client event notification message as an electronic mail message, a short messaging service (SMS) message, a multimedia messaging service (MMS) message, or a social networking service (SNS) message.

16. An article of manufacture comprising a storage medium containing instructions that when executed enable a system to:

receive an external event notification message with a publisher entity event for a publisher entity;

select a custom event receiver component associated with a publisher entity from among multiple custom event receiver components; and

send the external event notification message to the selected custom event receiver component.

17. The article of manufacture of claim 16, further comprising instructions that when executed enable the system to select the custom event receiver component for the external event notification message based on a globally unique identifier (GUID) for the publisher entity associated with the external event notification message.

18. The article of manufacture of claim 16, further comprising instructions that when executed enable the system to invoke a code callout arranged to perform custom logic in response to the publisher entity event.

19. The article of manufacture of claim 16, further comprising instructions that when executed enable the system to send a client event notification message to a client application associated with a subscriber entity subscribed to the publisher entity.

20. The article of manufacture of claim 16, further comprising instructions that when executed enable the system to send a client event notification message to a client application associated with a subscriber entity subscribed to the publisher entity, the client event notification message comprising an electronic mail message, a short messaging service (SMS) message, a multimedia messaging service (MMS) message, or a social networking service (SNS) message.