>Recently, there has been several threads on maintaining the state of a Web Service. I would like to mention that I wrote a 2nd article on that topic in our July issue of the magazine. SOAP 3 provides a greater flexibility in achieving that task.

Yes, I give it a quick look, and seems cool, congrats.

>The article mentions one approach which is by the use of the ASP intrinsic objects, from within VFP, combined with the management of a cookie.

Yes sawn, but I would like to achieve this withouth ASP, just VFP against VFP, I did a workaround that works but I prefer to dig more into this. Anyway in the SOAP3 doc says (Server-Side Data Flow) "Note that SOAP Toolkit supports only stateless programming model. That is, for each SOAP request, the COM object is created and released."

Also the SOAP 3 has some other good improvements like:

- Support for attachments
- more datatypes in the WSDL and a User-Defined Data Type Mappers.

SOAP3 seems cool