A notification represents a single, live notification created by a service executing atop the service platform. Individual notification details, e.g. a related global transaction ID, comprise its content. No notification details may be mutated after notification registration.
A notification is uniquely identified by combining its requester, service, and correlator values.
The globalTransactionID is the transaction in which a service registered the notification. The service registers the notification on behalf of a requester when the requester invokes a particular service and operation. The correlator is provided in any notification delivery attempts to allow a requester to associate notification deliveries with the notification setup activity.
A single notification may involve one or more operationTargets, which usually correspond to requester identities or characteristics the service monitors on behalf of the requester.
Notification delivery attempts occur when the service has "seen" an interesting network event for an operationTarget relative to a particular notificationCriterion. Delivery attempts use the specified notificationPortTypeName defined in the notificationPortTypeNamespace, and they are directed to the notificationEndPoint. Services may allow forced teardown of notifications by implementing and providing an adminSupportEndPoint for use by an administrator.
A notification's lifetime is bounded by its startTimeInMillis and its endTimeInMillis. Prior to expiration according to endTimeInMillis, a notification may complete by having attempted delivery of more than maxCountPerTarget notifications. Any two subsequent notifications must be separated by at least minPeriodInMillis.
Each subelement defines its own content semantics and may define default behavior/semantics when nill.
![]() ![]() |
|
<...>
End Sequence |
![]() |
|||||||
|
![]() |
|
![]() |
![]() |
![]() |