OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [wsrp] [CR313] - Clarify cookie guidance

Here is some motivation for this change

a. Reprocessing a request means that the Consumer has to send the same 
message again, incurring an extra roundtrip.

b. Reprocessing prevents us from using MIME attachments for markup 
requests. For instance, if a Consumer wants to resend a MIME request for 
performBlockingInteraction (hopefully with WSRP2.0) with uploaded data 
as an attachment, it will have to keep a copy of the attachment in 
memory for resending purposes. This cannot always be done, particularly 
with large uploads.

The same issues apply for InvalidSession fault too, but CR312 
discourages Producers from returning InvalidSession fault.



Rich Thompson wrote:
> Document: Specification
> Requested by: Subbu Allamaraju
> Section: 6.4 initCookie() Operation
> Page: 31
> Old Text:
> New Text: (addition at the end of line 15) However, since such 
> reprocessing usually incurs additional processing and network overhead, 
> Producers are encouraged to process the request as usual and return new 
> cookies along with the response. Consumers MUST process and resupply 
> such cookies as per Section 3.11.
> Compatibility Issues: This change does not affect the Producer behavior. 
> Section 3.11 already requires Consumers to process and return such cookies.
> Reasoning: This change clarifies brings up the issue of possible 
> negative impacts of reprocessing, and provides guidance on how best to 
> handle invalid cookies.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]