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 6551 - Transfer - Message processing time exceeded
Summary: Transfer - Message processing time exceeded
Status: CLOSED WONTFIX
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Transfer (show other bugs)
Version: FPWD
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Geoff Bullen
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: needsAction
Depends on:
Blocks:
 
Reported: 2009-02-09 16:20 UTC by Geoff Bullen
Modified: 2009-07-21 21:19 UTC (History)
1 user (show)

See Also:


Attachments

Description Geoff Bullen 2009-02-09 16:20:43 UTC
It is not clear in the spec what will happen if the message processing time is exceeded during the course of a (so far) successful multiple update via a PUT operation.  Are there other cases like this that should be explained?
Comment 1 Robert Freund 2009-02-11 07:59:29 UTC
Pending Action-13
Comment 2 Robert Freund 2009-03-12 17:43:11 UTC
Processing time may be only one  reason that the operation was unable to complete. Applies to T as well as RT, RT might leverage resolution in T.
r-assign to T then re-visit
Comment 3 Robert Freund 2009-07-21 21:19:13 UTC
2009-07-21 CWNA