This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6672 - Transfer: Non deterministic behavior of PutResponse
Summary: Transfer: Non deterministic behavior of PutResponse
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Transfer (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on:
Blocks: 6594 6673
  Show dependency treegraph
 
Reported: 2009-03-09 19:46 UTC by Doug Davis
Modified: 2009-06-23 23:59 UTC (History)
0 users

See Also:


Attachments

Description Doug Davis 2009-03-09 19:46:18 UTC
PutResponse allows for the current representation to be excluded
if it matches what was passed in on the Put request.  However, it also
allows for extension elements to be there.  Given the presence of just
one element, how does the client know if this one element is the 
current representation or an extension?

proposal: unless some extension is defined, the PutResponse should be
limited to just zero or one child elements under the PutResponse element.

In other words, no extension by default:
zero children == new representation is what was passed in on the request
one child == here's the new representation.
Comment 1 Robert Freund 2009-03-12 02:10:28 UTC
2009-03-11
proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0063.html
Comment 3 Robert Freund 2009-05-13 08:01:51 UTC
resolved on 2009-05-12 with proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Apr/att-0162/I6594-6672-6673-prop-ibm.doc