I have added a Broadcast method to distribute in guaranteed order a single message to multiple destinations. If one of those destinations is down, message delivery will resume when it becomes available again. If the message cannot be delivered in 24 hours, the the message will get logged to the failed log.
The new version of this library also creates send, read and failed log files by minute to assure the files are not too large when there is a very high number of messages flowing. It will also remove the sent and read files after 48 hours, a value you can change in the constructor.
Get the NuGet package here. Or check out the code on GitHub. Here’s some test code that demonstrates how these features work. (Update: the 1.2.2 package just published adds CountOutbound and CountInbound properties to allow you determine if your queues are getting backed up and more receiving or less sending should occur based on the limits you choose.)
[TestMethod] //test of send while dest down
public void DestDownTest()
var q1Address = new Address("qd1pipe");
var q2Address = new Address("qd2pipe");
using (var q1 = new MessageQueue("qd1", q1Address, @"c:\temp\qd1"))
q1.Send(q2Address, "hello world 1");
Thread.Sleep(200); //destination not available
q1.Send(q2Address, "hello world 2");
// now fire up the destination - simulating dest down
using (var q2 = new MessageQueue("qd2", q2Address, @"c:\temp\qd2"))
var msg = q2.Receive();
Assert.AreEqual(msg.MessageString, "hello world 1");
msg = q2.Receive();
Assert.AreEqual(msg.MessageString, "hello world 2");
[TestMethod] //test of broadcast to multiple destinations
public void BroadcastTest()
var q1Address = new Address("qb1pipe");
var q2Address = new Address("qb2pipe");
var q3Address = new Address("qb3pipe");
var q4Address = new Address("qb4pipe");
using (var q4 = new MessageQueue("qb4", q4Address, @"c:\temp\qb4"))
using (var q3 = new MessageQueue("qb3", q3Address, @"c:\temp\qb3"))
using (var q2 = new MessageQueue("qb2", q2Address, @"c:\temp\qb2"))
using (var q1 = new MessageQueue("qb1", q1Address, @"c:\temp\qb1"))
var msg2 = q2.Receive();
var msg3 = q3.Receive();
var msg4 = q4.Receive();
// confirm message received is the same
If you find it helpful, please give me a shout. If you want a change, shout louder.
I finally got around to fixing the code samples on the ServiceWire wiki on GitHub.
If you don’t know what ServiceWire is, please check it out and give it a try—download the NuGet package today. Be sure to read how easy it is to use on the Getting Started page.
I’d love to hear from you. Like it? Hate it? Want it to do something it doesn’t do?
ServiceWire is a very fast and light weight service host and dynamic client library that simplifies the development and use of high performance remote procedure call (RPC) communication between .NET processes over Named Pipes or TCP/IP.
The DuoVia.Net library has progressed significantly. But everyone I work with who uses it balks at the name. So I’ve renamed it. And I like the name very much. I hope you do too. It is ServiceWire. This name more aptly describes intuitively what the library does. Hopefully this will help with adoption and participation.
I’ve laid out the documentation wiki on that site and will spend the next few days or weeks getting it completely fleshed out. The code is in a new repository and there is a new NuGet package which, with the exception of namespaces, is at perfect parity with DuoVia.Net version 1.5.0.
I’m very interested in getting your feedback on ServiceWire, the name and the library.