Hi Thomas,
I read the mailing list and found your reply to "Stateful Web Services" stating that the SOAP header solution to maintaining state would be the right approach rather than the Cookie-based approach. I could maintain session and application scope using the HTTP cookies set on the client side and session/application scope on the server side. Could you kindly explain in detail the Header-based approach?
Sateesh.
[EMAIL PROTECTED] wrote:
If you are using Axis for your web service, setting the scope to session will turn cookie handling on from the server side point of view (Axis will use the HTTPSession features of the servlet container). On the C# client side, you have to create the cookie container for your service object to turn cookie on as well, and that is it, no need for anything else.
If you do a couple of searches in the mailing list archive you will find more details on all that for sure.
Thomas
-----Original Message-----
From: Sateesh Ayyagari [mailto:[EMAIL PROTECTED]
Sent: Monday, February 10, 2003 1:57 PM
To: [EMAIL PROTECTED]
Subject: Maintain Session with .NET and AXIS
Hi,
I have a question regarding maintaining session. How do we maintain session for a Java Web Service which is consumed by a C# client? Any links would be appreciated.
Sateesh.
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now
Do you Yahoo!?
Yahoo! Web Hosting - establish your business online
