>Well, this would bring a totally new dimension. For example, keeping a connection state would allow us to offer something like UT is offering from the Web but locally. Thus, instead of passing username and password for each method, we'll pass them once and them keep the connection opened for all other calls. Kinda like the session object of ASP.

So, really, you would be accomplishing the EXACT same thing as now, just passing less parameters in your methods. That doesn't sound like a whole new dimension. Sorry.

FWIW, check out my reply to Alan in this thread, its possible to create a statefull wrapper to your web service. You could offer one of these for the UT webservice.