Techniques to manage remote events

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.

1 .- 20 . (canceled) 
     
     
         21 . A computing system, comprising:
 a processor circuit; and   a remote event application operative on the processor circuit to manage remote event notifications between a publisher entity and a subscriber entity, the remote event application when executed by the processing circuit causing the computing system to:
 receive an external event notification message identifying a publisher entity event, wherein the publisher entity event is an update to data stored in a data source maintained by the publisher entity; 
 select a custom event receiver component corresponding to the publisher entity from among multiple custom event receiver components, wherein the selected custom event receiver component comprises at least one code callout for performing at least one operation; 
 automatically invoke the at least one code callout to perform the at least one operation, wherein the at least one operation is responsive to the publisher entity event; and 
 send a client event notification message to a subscriber entity upon performing the at least one operation, wherein the subscriber entity is not in direct communication with the publisher entity. 
   
     
     
         22 . The computing system of  claim 21 , further comprising a representational state transfer (REST) based input point. 
     
     
         23 . The computing system of  claim 21 , the data source corresponding to an external application of the publisher entity. 
     
     
         24 . The computing system of  claim 23 , the publisher entity event comprising a change in state of the data stored by the data source for the external application. 
     
     
         25 . The computing system of  claim 21 , wherein the custom event receiver component for the external event notification message is selected based on a globally unique identifier (GUID) for the publisher entity associated with the external event notification message. 
     
     
         26 . The computing system of  claim 21 , wherein the at least one code callout is arranged to perform custom logic in response to the publisher entity event. 
     
     
         27 . The computing system of  claim 21 , further comprising:
 retrieve a notification parameter associated with the subscriber entity; and   send the client event notification message to a client application associated with the subscriber entity, wherein the subscriber entity subscribes to the publisher entity.   
     
     
         28 . The computing system of  claim 21 , further comprising an event management component operative to manage a subscription between the publisher entity and the subscriber entity. 
     
     
         29 . The computing system of  claim 28 , the event management component operative to manage a level of reliability for external event notification messages. 
     
     
         30 . The computing system of  claim 28 , wherein the event management component is operative to retrieve a reliability parameter representing a reliability level associated with the publisher entity, further comprising:
 process the external event notification message based on the reliability parameter.   
     
     
         31 . The computing system of  claim 30 , comprising a set of message handling parameters associated with the reliability parameter, the message handling parameters comprising one or more of:
 a duplicate message parameter indicating whether to accept or reject duplicate external event notification messages;   a standby server parameter indicating whether to send the external event notification message to a standby server when a primary server is non-operational; and   a replay parameter indicating whether to replay the external event notification message when an error condition is detected when processing the external event notification message.   
     
     
         32 . A computer-implemented method, comprising:
 receiving, at a computing device, an external event notification message identifying a publisher entity event, wherein the publisher entity event is an update to data stored by a publisher entity, wherein the publisher entity is remote from the computing device;   selecting, at the computing device, a custom event receiver component corresponding to the publisher entity from among multiple custom event receiver components, wherein the selected custom event receiver component comprises at least one code callout for performing at least one operation;   automatically invoking the at least one code callout by the custom event receiver component to perform the at least one operation, wherein the at least one operation is responsive to the publisher entity event; and   upon performing the at least one operation, sending a client event notification message from the computing device to a subscriber entity operating on a client device, wherein the subscriber entity is not in direct communication with the publisher entity.   
     
     
         33 . The computer-implemented method of  claim 32 , further 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.   
     
     
         34 . The computer-implemented method of  claim 32 , wherein the code callout is arranged to perform custom logic in response to the publisher entity event. 
     
     
         35 . The computer-implemented method of  claim 32 , further comprising:
 sending the client event notification message as one of: an electronic mail message, a short messaging service (SMS) message, a multimedia messaging service (MMS) message, and a social networking service (SNS) message.   
     
     
         36 . A computer system comprising:
 a processing unit; and   a memory storing computer-executable instructions for causing the computer system to manage external event notifications comprising:
 receiving an external event notification message identifying a publisher entity event, wherein the publisher entity event is an update to data stored by the publisher entity; 
 selecting a custom event receiver component corresponding to the publisher entity from among multiple custom event receiver components, wherein the selected custom event receiver component comprises at least one code callout for performing at least one operation; 
 automatically invoking the at least one code callout to perform the at least one operation, wherein the at least one operation is responsive to the publisher entity event; and 
 upon performing the at least one operation, sending a client event notification message to a subscriber entity, wherein the subscriber entity is not in direct communication with the publisher entity. 
   
     
     
         37 . The computer system of  claim 36 , further 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.   
     
     
         38 . The computer system of  claim 36 , wherein the code callout is arranged to perform custom logic in response to the publisher entity event. 
     
     
         39 . The computer system of  claim 36 , further comprising:
 sending the client event notification message to a client application associated with the subscriber entity subscribed to the publisher entity.   
     
     
         40 . The computer system of  claim 36 , wherein the client event notification message comprises one of: an electronic mail message, a short messaging service (SMS) message, a multimedia messaging service (MMS) message, and a social networking service (SNS) message.