Ayende @ Rahien

Davy Brion commented on Batching WCF Calls

Tue, 01 Jul 2008 20:00:02 GMT

ok, now you no longer need to explicitly register Requests & Replies you can find the new implementation here: http://davybrion.com/blog/2008/07/batching-wcf-calls-take-2/

Davy Brion commented on Batching WCF Calls

Mon, 30 Jun 2008 08:51:14 GMT

the specific service interfaces are there in case you prefer to just call one specific method... it's also good for 'discoverability' i actually like to have one class per message. depending on how many messages you have regarding products, it could be a huge class if you handled all of them in the same class. Also, one class per message makes it really easy to have the container inject each dependency you need

Daniel commented on Batching WCF Calls

Mon, 30 Jun 2008 08:33:31 GMT

I like the way it is done in NServiceBus - all you need is three interfaces (IMessage, IHandler, IBus). Just substitute the IBus for your IService and your done. Why bother to add specific service interfaces like IProductsService? The interface IHandler has another advantage - one class can implement many of these, so you can have e.g. all product messages handling code in one class (you don't need one class per message anymore).

Davy Brion commented on Batching WCF Calls

Mon, 30 Jun 2008 07:38:18 GMT

yea i'm not happy with the explicit registering either... i really want something better there so i'll look into your suggestion ;)