>>I don't think so, you are responsible for managing that e.g. you can have a table called sessions that have a sessionid or cookie has key another field that is the userid an another one to hold the expiredate plus additional information that you need on the login method insert or update that entry and return the key to the client all the other methods will look into that table to get the user id and additional information.
>
>The process of managing it is not the issue. What I am looking for is the ability to avoid passing an identifier so I'll recognize my user. As either InternetOpenUrl() or the Microsoft Web Browser control are both making calls to the same URL as well, I thought I could benefit of what's in the memory locally for the Web Service assuming I would issue a call that will store a cookie prior to calling the Web Service. Anyway, I'll give it a try. We never know.

Another thing that you may also look in is on the SOAP toolkit user guide under advance option look the Handling SOAP Headers documentation perhaps this can help you.