>For you, as I can see, you're mostly only using that method.

Its not just for me, but I'm using 2. Keep in mind your use cases for these Web Services. If you are putting out the web service thinking that people that use them are interested in completely recreating a UT interface, thats not the point. The point is to get the data you need quickly. For most people, that means cutting down on superflous round trips to the server.

>Keep in mind that other people are using them all.

Really? Who's using all 17 and for what?

>I wouldn't want to apply such a design and have to support it as well. Duplicating all methods in order to offer one version as is and one version with authentication is just not something I will support.

I understand your hesitance, but it wouldn't be that tough. You can write a program to build a subclass based on your object and add two parameters to every method, authenticate, and dodefault().