>>>That doesn't sound like a whole new dimension. Sorry.
>>Well, we could play with words. <s>
>
>I'm still trying to figure out what stateful objects are capable of that stateless aren't. What is it?
>
>I will admit, it would make it easier to use, form an interface standpoint, but it shouldn't be capable of anything new. I'm also sure that scalaibiliy, privacy, and security would suffer some what.
>
>You could easily create your own session mechnism with a VFP table and a session id (sys(2015)).
>
>>Yes, I've seen that reply but I'm not sure exactly how to use it.
>
>Well, you could create create a VFP class that has a method for every method in your web service, plus a login method. The login method would save the username and password into properties of that object.
>
>Then, everytime a method (like GetNews) is called, you don't need to pass the username and password. The GetNews method will then call the WebService's getNews method and pass the username and password from the properties it set in the Login().

Yes, of course, such wrapper could do it. But, at the server level, the situation is still the same. For each transaction, we have to identify the user and set all the related properties again.