[rabbitmq-discuss] Deprecating WCF library
marcos.torres at gmail.com
Mon Nov 25 15:31:23 GMT 2013
Sorry, I haven't read this before.
I deprecating you mean remove them or simply provide no further
improvements? I'm on my very first RabbitMQ project using .NET libraries
and while I'm not using any of the message patterns, It was really helpful.
This is not the same for WCF which I consider a dead end.
On Mon, Nov 25, 2013 at 11:58 AM, Emile Joubert <emile at rabbitmq.com> wrote:
> 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.
> 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.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss