https://github.com/shuttle/shuttle.esb.netmq
NetMQ implementation for use with Shuttle.Esb.
https://github.com/shuttle/shuttle.esb.netmq
Last synced: about 2 months ago
JSON representation
NetMQ implementation for use with Shuttle.Esb.
- Host: GitHub
- URL: https://github.com/shuttle/shuttle.esb.netmq
- Owner: Shuttle
- License: bsd-3-clause
- Created: 2019-07-15T05:00:26.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2020-02-14T10:27:30.000Z (over 5 years ago)
- Last Synced: 2025-02-02T07:28:54.470Z (4 months ago)
- Language: C#
- Size: 89.8 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Shuttle.Esb.NetMQ
NetMQ implementation for use with Shuttle.Esb. Since NetMQ/ZeroMQ does not provide a queue as such this mechanism is used to *front* other queues or to make use of in-memory queues.
## NetMQQueue
The queue configuration is part of the specified uri, e.g.:
``` xml
```
| Segment / Argument | Default | Description | Version Introduced |
| --- | --- | --- | --- |
| host-ip | none | The IP address of the Shuttle.Esb.NetMQ.Server that will process all requests. | |
| port | none | The port on which the Shuttle.Esb.NetMQ.Server will be listening for connections. | |
| queue-name | none | The queue name that needs to be accessed. | |
## Shuttle.Esb.NetMQ.Server
The server is required to listen to any requests from clients. Since the server acts as a *go-between* for an actual queue you would need to specify the `uri` of the actual queue represented by a `name` using the application configuration file:
``` xml
```