--- In [email protected], JP Morgenthal <[EMAIL PROTECTED]> wrote: > > Exactly. I wish more people would understand this impedance > mismatch. A service should be a coarse-grained business entity, > and not a fine-grained API responsible for supporting a UI.
+1 > When I designed my SOA for supply-chain management, none of my > service could be used directly by a RIA without significant > processing overhead in the client, so I had to develop a business- > process layer to mediate between the two. I'm inclined to place that service-app mapping stuff as shared components of the UI/presentation/app layer. But a distinct layer works too--as long as those components aren't referred to as "services" which would really confuse things. > Otherwise, I can't see the difference between an API and a service > and I fundamentally believe these two things are not the same and > that one is not a subset of the other. +1 again. -Rob
