This project is read-only.


Feb 12, 2009 at 3:06 PM
I'm interested in using this with WCF endpoint.  Has anyone looked into this?
Feb 14, 2009 at 10:17 PM
I've thought about this over and over again. Not just with this library, but with any of the various similar libraries out there. The main issue is that WCF requires each of its "endpoints" or interfaces to implement a particular message contract. Libraries like this one, it's parent, NSB, Mass Transit, etc. are queue based, and so there is a conceptual divide - a message that could match any number of possible contracts is placed in a single queue, and dispatched to some appropriate handler when the message is pulled off the queue. The only way I can think of to integrate something like this with WCF is to have a generic WCF contract that has a string to hold the XML payload of the message, which wouldn't be so bad, but then what would you get out of using WCF?