I’m torn as it does solve a very real problem, but at the same time, it hinders discovery of operations. To some extent, this is offset by the request classes, but there is a danger here of not knowing exactly how much data you need unless you create a request per call (whereas a method signature is much more explicit in terms of the parameterization).

good to know

if you ever run into problems with it or have any questions, just mail me

Pretty good. We have replaced Castle with Hiro and put our own implementation of KnowTypesProvider, but other than that, your code works just fine.

the complexity is isolated within the infrastructural classes… the actual request handlers are as simple as they can be, so i don’t see why it would be over engineering

Your design is interesting though I have my reservations about the value addition it does versus the complexity it brings. The main driving point for me in your arguments is – coarse / fine grained operations & both have their own disadvantages. I would still prefer going for coarse grained the reason being they are more explicit, easy to understand & consume. I agree it would add duplication of code (considering it might be duplicated for different clients / scenarios) but this duplication is more of instantiation & packing (not any algorthmic one). I would have fine grained repositories which inturn would create data & expose them through coarse grained contracts. Your solution looks like over engineering.

ah, cool! how has it worked out so far?

We started to use it from the moment I read your blogpost

dealing with channels requires some housekeeping code… if you don’t want to see that repeated throughout your codebase, you put that code in a class (in this case, the proxy type) and just use instances of that class.

Is there a reason you are using a static proxy instead of the Channel Factory directly?

Considering you control both the end-points wouldn’t a Channel Factory be simpler as all you need to do is share the contracts assembly instead of re-generating the proxy everytime you add/change an operation?