Add subscription feature for event-driven architectures.
An event is triggered for Subscriptors to received whenever an inbound dispatch (which may be sent to self) is configured with the header gateway setted as broadcast.
Subscriptions can be addressed at any level of the REST hierarchy. For example, given the following REST calls:
1 - GET User/:id/Article
2 - PUT User/:id
...a subscription on User will be triggered in every event, while a subscription in User/:id/Article will be retrieved only in the first one.
Add subscription feature for event-driven architectures.
An event is triggered for Subscriptors to received whenever an inbound dispatch (which may be sent to self) is configured with the header
gateway
setted asbroadcast
.Subscriptions can be addressed at any level of the REST hierarchy. For example, given the following REST calls:
...a subscription on
User
will be triggered in every event, while a subscription inUser/:id/Article
will be retrieved only in the first one.