>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.

I have the log here or every hit. Many users are using our Web Service to execute a bunch of methods in a row to get some requested info.

>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().

We're not using that design. We're working on avoiding that approach at most.