 | IDispatcherQueueManagerService Interface |
A service which is responsible for storing messages in a reliable place for dispatching
Namespace: SanteDB.Core.Queue
Assembly: SanteDB.Core.Api (in SanteDB.Core.Api.dll) Version: 2.2.1
SyntaxThe IDispatcherQueueManagerService type exposes the following members.
Properties| Name | Description | |
|---|---|---|
 | ServiceName |
Gets the service name
(Inherited from IServiceImplementation.) |
Methods| Name | Description | |
|---|---|---|
 | Dequeue |
Dequeues the last added item from the persistent queue
|
| DequeueById |
De-queue a specific message
|
| Enqueue |
Enqueue the specified data to the persistent queue
|
| GetQueueEntries |
Get all queue entries
|
| GetQueueEntry |
Get the specified queue entry
|
| GetQueues |
Gets the queues for this system
|
| Move |
Move an entry from one queue to another
|
| Open |
Opens the specified queue name and enables subscriptions
|
| Purge |
Purge the queue
|
| SubscribeTo |
Subscribes to queueName using callback |
| UnSubscribe |
Remove the callback registration
|
Remarks
Whenever SanteDB sends messages to another system using messaging, there is no guarantee that the remote endpoint will be available,
or accessable, etc. Therefore all messages which are sent (dispatched) to a remote system are first queued using this wrapper service.
The purpose of the dispatcher queue is the store the outbound message locally in some persistent place, then to notify any listeners that a new message is ready for sending. If the message cannot be sent, then the sending service should place the message back onto the queue or onto a dedicated deadletter queue.
See Also