[Bug 9608] New: Support WS-Management's Enumerate Count feature

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9608

           Summary: Support WS-Management's Enumerate Count feature
           Product: WS-Resource Access
           Version: LC
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Enumeration
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: gilbert.pilz@oracle.com
         QAContact: public-ws-resource-access-notifications@w3.org


Description: WS-Management v1.1 [1] Section 8.2.2 defines an extension to
WS-Enumeration wherein a consumer is provided with an estimate of the number of
items in an enumeration. This allows consumers to allocate the resources
necessary to store and process the results of the ensuing Pull operations in a
more efficient manner than what might be possible with a pull/store/resize/copy
pattern.
It is the opinion of the WS-Man WG that this feature is sufficiently general as
to warrant inclusion in the base specification. The WS-Man WG requests that
WS-RA WG incorporate this extension as an optional feature of WS-Enumeration.

[1] http://www.dmtf.org/standards/published_documents/DSP0226_1.1.pdf

---

Proposal: Although WS-Management applies this extension to both the
wsen:Enumerate and wsen:Pull operations, this proposal narrows the application
to an option of the wsen:Enumerate/wsen:EnumerateResponse exchange.

1. Modify the Enumerate request to include an optional element or define a soap
header that is equivalent to wsman:RequestTotalItemsCountEstimate.

2. Modify the EnumerateResponse message to include an element or header  that
is equivalent to wsman:TotalItemsCountEstimate.

3. Define an additional fault to cover the case where a consumer requests the
enumeration count from a data source that does not support this feature.

4. Add a parameter to the wsenu:DataSource assertion to indicate that an
endpoint supports the Count feature.

5. Define a mechanism to allow a client to specify whether the request should
be performed with or without the use of this feature in a way similar to the
way mustUnderstand works.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

Received on Wednesday, 28 April 2010 21:49:34 UTC