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 6422 - RT - Introduces An Ad Hoc Boxcarring Mechanism
Summary: RT - Introduces An Ad Hoc Boxcarring Mechanism
Status: CLOSED WONTFIX
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: ResourceTransfer (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: hasProposal
Depends on:
Blocks:
 
Reported: 2009-01-14 05:43 UTC by Geoff Bullen
Modified: 2009-09-30 09:59 UTC (History)
1 user (show)

See Also:


Attachments

Description Geoff Bullen 2009-01-14 05:43:13 UTC
The WS-ResourceTransfer specification introduces boxcarring or batching multiple operations within a single SOAP message.  In general, boxcarring causes a lot of problems - especially with transactional rules, sequencing micro operations, fault handling, semantics of the SOAP Action URI - reduces to just "Do Stuff", etc.

The SOAP specifications do not explain how boxcarring is performed. The WS-ResourceTransfer specification specifies an one-off boxcarring mechanism.

Perhaps work associated with this feature would be better suited to a separate specification, where all the fine details can be worked out and the result can be used by many specs?
Comment 1 Robert Freund 2009-03-12 17:52:13 UTC
Highlights that RT should follow idempotency properties of T, then might depend on specification of restrictions as to frags permitted