...
Getting Started with NMS
The NMS API (.Net Message Service API) providers a standard .NET interface to Messaging Systems. There could be multiple implementations to different providers (including MSMQ).
NMS API currently supports all of the features of JMS in a simple pure C# API and implementation apart from XA. Current features include
- creating & disposing of connections, sessions, producers, consumers
- sending of messages to topics, queues with durable or non durable along with temporary destination support
- synchronous consuming (blocking receive, receive with no wait or receive with a timeout)
- asynchronous consuming (adding a MessageListener to be dispatched in the thread pool)
- JMS message header support along with custom properties
- Text, Bytes, Stream and Map message support
- support for JMS transactions (sending and acknowledging multiple messages in an atomic transaction)
- redelivery of messages in rollbacks up to some configured maximum redelivery count
- Optional Queue browser interface for providers that can support it.
- Optional .NET Distributed Transaction Support for providers that can support that.
A provider implementation based on a pure C# implementation of OpenWire is provided for working with the Apache ActiveMQ broker. There are other provider implementations for working with Stomp, TIBCO, Microsoft Message Queue (MSMQ), and Windows Communication Foundation (WCF).
If you are curious you can browse the source code and tests for the entire project or follow the links in the next section to download a specific NMS Providerprovides your client a common API model for working with Message Oriented Middleware, but to make use of the API you need to download one of the NMS Provider libraries. The NMS Providers libraries are what makes it possible for your code to connect to your Message Broker. Follow the links below to read more about the NMS Provider for your Message broker and download a release bundle.
| Include Page | ||||
|---|---|---|---|---|
|
...