|author||Havret <firstname.lastname@example.org>||Fri Sep 27 15:45:55 2019 +0200|
|committer||Havret <email@example.com>||Fri Sep 27 16:02:54 2019 +0200|
AMQNET-617: Support Message Selectors
The goal of this project is to combine the .NET Message Service API (NMS) with the Advanced Message Queuing Protocol (AMQP) 1.0 standard wireline protocol. Historically, the Apache community created the NMS API which provided a vendor agnostic .NET interface to a variety of messaging systems. The NMS API gives the flexibility to write .NET applications in C#, VB or any other .NET language, all while using a single API to connect to any number of messaging providers. The Advanced Message Queuing Protocol (AMQP) is an open and standardized internet protocol for reliably passing messages between applications or organizations. Before AMQP became a standard, organizations used proprietary wireline protocols to connect their systems which lead to vendor lock-in and integration problems when integrating with external organizations.
The key to enabling vendor independence and mass adoption of technology is to combine open source APIs and standard wireline protocols which is precisely what this project is all about. Here's how AMQP 1.0 support within NMS helps the .NET community:
If you are a .NET developer that doesn't want to be locked into a messaging implementation then get engaged with this project. Here you will find the open source code base and please provide comments and make your own enhancements. The project will be folded into the Apache community once fully mature.
Apache-NMS-AMQP uses AmqpNetLite as the underlying AMQP 1.0 transport Protocol engine.
Apache-NMS-AMQP should bridge the familiar NMS concepts to AMQP protocol concepts as described in the document amqp-bindmap-jms-v1.0-wd09.pdf. So in general most of the top level classes that implement the Apache.NMS interface Connection, Session, MessageProducer, etc create, manage, and destroy the amqpnetlite equivalent object Connection, Session, Link, etc.
|TLS/SSL||Y||Configuration is supported using transport properties.|
|Client Certificate Authentication||Y||Configuration is supported using transport properties.|
|Distributed Transactions (INetTxConnectionFactory, INetTxConnection, INetTxSession)||N|
|IObjectMessage||Y *||Amqp value object bodies and dotnet serializable object bodies are supported.|
|IConnection||Y||The ConnectionInterruptedListener event and the ConnectionResumedListener are not supported.|
|ProducerTransformerDelegate||N||Any member access should throw a NotSupportedException.|
|ConsumerTransformerDelegate||N||Any member access should throw a NotSupportedException.|
|IMessageProducer||Y *||Anonymous producers are only supported on connections with the ANONYMOUS-RELAY capability.|
|MsgDeliveryMode.Persistent||Y||Producers will block on send until an outcome is received or will timeout after waiting the RequestTimeout timespan amount. Exceptions may be throw depending on the outcome or if the producer times out.|
|MsgDeliveryMode.NonPersistent||Y||Producers will not block on send nor expect to receive an outcome. Should an exception be raised from the outcome the exception will be delivered using the the connection ExceptionListener.|
|IMessageConsumer||Y *||NoLocal filter is not supported.|
|IQueueBrowser||N||The provider will throw NotImplementedException for the ISession create methods.|
|Configurable NMSMessageID and amqp serializtion||N||For future consideration. The prodiver will generate a MessageID from a sequence and serialize it as a string.|
|Flow control configuration||N||For future consideration. The provider will use amqpnetlite defaults except for initial link credits which is 200.|
|Object Deserialization Policy||N||For future consideration. The provider considers all Dotnet serialized objects in Object Message bodies are safe to deserialize.|
This software is licensed under the terms you may find in the file named “LICENSE” in this directory.