Hi,
I would appreciate some guidance on modelling services and operations in WCF.
I have a series of business domains, each with bespoke methods that I want to able to use over WCF. I guess an OO view would be something like:
interface IBusinessDomain1
{
MyClass1 Method1(...)
MyClass2 Method2(...)
}
interface IBusinessDomain2
{
MyClass3 Method3(...)
MyClass4 Method4(...)
}
My natural inclination was to make each interface a service and each method an operation, the problem I have with this is that operations within individual domains might well need quite different binding configurations. i.e. Method1 might need to be synchronous, Method2 might need to be asynchronous.
When definining services and operations for WCF, would a better approach be to think in terms of the data types and the way data needs to be sent? Perhaps group methods from all business domains that will need to work in a particular way and have those in one service? I wonder how other people have tackled similar scenarios?
Most WCF tutorials and examples I have seen tend to use fairly trivial models, often a 'calculator' service offering 'add', 'subtract' etc. operations which all share the same binding.
Some advice on how to approach defining my services and operations would be most appreciated, or just some links to further reading as I cannot find much.
Thanks in advance, Will