(Click to open topic with navigation)
When event commands are executed (asynchronously), the success or failure of the operation is communicated back to the initiator via a notification. When an event is created, you may specify the Notify option which will associate a notification method with the event. Currently there is only one DeliveryMethod implemented which is Store. With the Store delivery method, command response information is stored as instances of the Notification object. These messages can later be retrieved by the initiator via a Notification Query. Payments can also route a notification method down to their associated events via a Notify option.
The notification attributes include Id (auto-generated), Type, Event, Status, Code, Message, Key, Recipient, EndTime and CreationTime. Stored notifications can be queried on any of these conditions. The notification type distinguishes what type of command resulted in the notification (Fire or Failure). The notification key is the value of the primary key of the object instance that the command acted on (e.g. the Payment Id). The recipient could be a user name or any tag that identifies the intended reader for the notification. The Notification Query supports a Delete option, which if set to True, will delete the notifications after they have been queried. Additionally, stored notifications have an EndTime after which they are automatically deleted by Gold. The Notification actions include Send, Refresh, Create, Query, Delete and Modify.
There are two server configuration parameters which affect notifications: notification.deliverymethod which dictates which deliverymethod is used by default if unspecified and notification.duration which defines how long notifications stick around if the Store delivery method is used.