[rabbitmq-discuss] Deprecating WCF library

[Emile Joubert]

No objections were raised in response to this message below, so the
retirement process for the Java and .net message patterns libraries will
move forward.

In addition to the messagepatterns libraries, we are also considering
deprecating the RabbitMQ WCF binding. Evidence similarly suggests that
it is not being used much. Using the regular RabbitMQ .net client
library would be the suggested alternative. The .net library does not
suffer from the same limitations and is maintained more regularly.

To help us assess the impact, please let us know if you have any
objections to the WCF binding being deprecated.



-Emile



On 17/10/12 12:31, Emile Joubert wrote:

> We are considering deprecating the RabbitMQ Java and .NET
> messagepatterns libraries, as part of a cleanup exercise:
> 
> http://hg.rabbitmq.com/rabbitmq-java-messagepatterns/
> http://hg.rabbitmq.com/rabbitmq-dotnet-messagepatterns/
> 
> These libraries were meant to provide some higher-level abstractions on
> top of the regular Java and .NET libraries, but evidence suggests that
> they are not being used much. And they haven't had any updates for years.
> 
> Please let us know if you have any objections to both of these being
> deprecated.