W3C home > Mailing lists > Public > xml-dist-app@w3.org > August 2001


From: Paul Prescod <paulp@ActiveState.com>
Date: Mon, 27 Aug 2001 01:27:37 -0700
Message-ID: <3B8A0479.36514C4E@ActiveState.com>
To: xml-dist-app@w3.org
Francis Norton wrote:
> ...
> This seems a reasonable analysis of the current situation to me - but a
> more satisfactory alternative to this situation would be to define an
> official session key storage element in the SOAP header section. I think
> that this might satisfy an immediate and important user requirement,
> before less satisfactory solutions get frozen into de-facto standards.

Can you please clarify the requirement for cookies? A cookie is extra
information that is passed along with a request. A SOAP message uses an
extensible syntax designed to transmit arbitrarily complex information. 

 a) Why would you need to put the cookie in a header.

 b) What is the benefit in having a *standardized* cookie syntax rather
than transmitting the same information as a random XML element in your
favorite XML namespace. myns:mycookie

Or even better, you could just transmit the information represented by
the cookie explicitly (e.g. your customer id, your authentication
information, etc.).
Take a recipe. Leave a recipe.  
Python Cookbook!  http://www.ActiveState.com/pythoncookbook
Received on Monday, 27 August 2001 04:28:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:15 UTC