AMercer
11/11/2008 9:53:00 PM
> Now that's the problem. In my manager's view he thinks that each
> command should be a differencet WebService.
> I *MY* view I'd have a single WebService that provide methods to list
> from and add into our extension directory.
If you have a small number of developers, I see your point (sort of), but if
you have many, your manager may have it right because the project breaks up
naturally into pieces for independant development requiring (relatively) less
coordination.
For every well run project, there will be a regression test policy once you
get to O&M. In your approach, the smallest delivery will require a complete
regression test (or you can take short cuts), whereas your manager's approach
will require limited regression tests.
> But I can't translate the dificulty I see when people will be
> consuming this WebServices into proper words.
What difficulty? Efficiency maybe? Code duplication vs reuse? I think the
burden is on you to explain your problem a little more. So far, I don't see
any compelling argument in either direction.