I've commited an upgrade to the RabbitMQ libraries in Mono to version 1.6 bringing Mono in line with the latest from the RabbitMQ team.
I've been working on a couple of other pieces, mostly a reworking of the MessageQueue integration code in order to have Connection objects hang onto AMQP channels. Currently a new connection to the AMQP server is created for each request, which will obviously have an impact on latency. I'm holding off committing this work for now as I want to use .NET 2.0 features which will be easier post the 2.6 release.
3 comments:
.NET 2.0 features have been supported in mono since mono 1.2. We're now about 20 releases after that, i think it's safe to rely on 2.0 features ;)
The only reason you should *not* use 2.0 features is if you find a bug in that feature which exists in currently shipping versions of mono.
Currently this work is deployed as part of Mono and currently needs to support 1.1 (changing this breaks many things). So if I want use 2.0 then I need to do a lot of #ifdefs to gracefully handle 1.0/1.1 support. After the 2.6 release 1.1 support will no longer be required so using 2.0 features will be much easier.
Ah yes, I see what you mean. I'm looking forward to .NET 1.0/1.1 being dropped alright. It'll be a great day!
Post a Comment