Abstract: The present disclosure prevents unnecessary delays during a notification delivery process in an event driven system. The unnecessary delays may be caused by waiting for event completion acknowledgments for an unbounded time. Notifications (event handle requests) may be dispatched to all interested parties in parallel. Then, handling acknowledgments from the interested parties may be gathered after a specific delay. Termination requests may be sent to non-responding parties in order to prevent indefinite waiting or an advertent notification cycle. Alternatively, non-responding parties may be removed from a list of listeners which have been registered as interesting parties for a software component in the event driven system.

Abstract: The present invention is directed to a method and system for preventing unnecessary delays during notification delivery process in an event driven system. The unnecessary delays may be caused by waiting for event completion acknowledgments for an unbounded time. Notifications (event handle requests) may be dispatched to all interested parties in parallel. Then, handling acknowledgments from the interested parties may be gathered after a specific delay. Termination requests may be sent to non-responding parities in order to prevent indefinite waiting or an advertent notification cycle. Alternatively, non-responding parties may be removed from a list of listeners which have been registered as interesting parties for a software component in the event driven system.

Abstract: The present invention is directed to a method and system for preventing unnecessary delays during notification delivery process in an event driven system. The unnecessary delays may be caused by waiting for event completion acknowledgments for an unbounded time. Notifications (event handle requests) may be dispatched to all interested parties in parallel. Then, handling acknowledgments from the interested parties may be gathered after a specific delay. Termination requests may be sent to non-responding parties in order to prevent indefinite waiting or an advertent notification cycle. Alternatively, non-responding parties may be removed from a list of listeners which have been registered as interesting parties for a software component in the event driven system.

Abstract: A system and method for distributing management events to external process is presented. A notification listener registers with a client notification service that resides locally with the notification listener. The registration includes one or more notification types in which the notification listener wishes to be notified. The client notification service configures a remote proxy located on a server to provide notification events to the client notification service that have one of the notification types. The remote proxy receives notification events from a server notification service, and provides the notification events to the client notification service. In turn, the client notification service provides the notification events to the notification listener. The remote proxy may be configured for push processing or pull processing.

Abstract: There is provided a method for employing a trigger point in a logic flow. The trigger point has at least one function associated therewith. A default strategy set is associated with the at least one function of the trigger point. The default strategy set has a capability of being replaced, in whole or in part, by a non-default strategy set. The strategy sets are for implementing the at least one function of the trigger point. The trigger point is dynamically configured, including establishing at least one context for the trigger point that respectively specifies a location of the strategy sets. The trigger point is executed when encountered during an execution of the logic flow, including selectively executing at least a portion of at least one of the default strategy set and the non-default strategy set based upon a current context from among the at least one context.

Abstract: A system and method for distributing management events to external process is presented. A notification listener registers with a client notification service that resides locally with the notification listener. The registration includes one or more notification types in which the notification listener wishes to be notified. The client notification service configures a remote proxy located on a server to provide notification events to the client notification service that have one of the notification types. The remote proxy receives notification events from a server notification service, and provides the notification events to the client notification service. In turn, the client notification service provides the notification events to the notification listener. The remote proxy may be configured for push processing or pull processing.

Abstract: There is provided a method for employing a trigger point in a logic flow. The trigger point has at least one function associated therewith. A default strategy set is associated with the at least one function of the trigger point. The default strategy set has a capability of being replaced, in whole or in part, by a non-default strategy set. The strategy sets are for implementing the at least one function of the trigger point. The trigger point is dynamically configured, including establishing at least one context for the trigger point that respectively specifies a location of the strategy sets. The trigger point is executed when encountered during an execution of the logic flow, including selectively executing at least a portion of at least one of the default strategy set and the non-default strategy set based upon a current context from among the at least one context.