CCR Provider Available for the Reactive Queue


Bnaya has released a new version of the RxContrib project which includes the Reactive Queue – an RX interface above a message queue.  This version has a provider for CCR ports as the underlying queue mechanism.  This provider supports a Port<T> for OnNext notifications, and PortSet<T, Exception> for both OnNext and OnError notifications.  To compile, make sure that you have a version of the CCR available (you can download it from here) and change the appropriate references in System.Reactive.Contrib.Ccr and System.Reactive.Contrib.UnitTests.  I’ll be doing some posts in the near future on how to use the...
no comments

Event Aggregator Pattern Using the Reactive Extensions


The Rx world is most definitely on fire!  Check out Jose’s short-and-sweet implementation of an Event Aggregator using RX.  And apparently, we’ll soon see it in Caliburn.  Let the good times roll!  (Also, check out Bnaya’s introduction and RxContrib). As the immortal Hannibal Smith once said - “I love it when a plan comes together”.
no comments

In-Memory Queues: Performance comparison between the CCR and the .NET Framework’s ConcurrentQueue


 Update:  See the notes for an important point about the 50,000 bytes / 100,000 messages case. Code for this post is available here.  See below for the link to the download containing the CCR DLL. So here’s the problem:  you need an in-memory queue in your application that can handle processing a large number (several thousands) of messages per second, using several enqueuing and dequeuing threads.  If you’re using .NET Framework 4.0 then you would immediately go for the new ConcurrentQueue class available in the System.Collections.Concrurent namespace.  But what if you’re...
tags: , , ,