W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > April 2010

[Bug 9609] New: Support WS-Management's optimization of Enumerations with small result sets

From: <bugzilla@jessica.w3.org>
Date: Wed, 28 Apr 2010 21:55:56 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-9609-2780@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9609

           Summary: Support WS-Management's optimization of Enumerations
                    with small result sets
           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


WS-Management v1.1 [1] Section 8.2.3 defines an extension to WS-Enumeration
wherein the initial Enumerate/EnumerateResponse exchange functions as an
implicit Pull/PullResponse exchange. This behavior is useful in cases where the
enumeration has such a small number of items that the initial EnumerateResponse
could reasonably include the entire result, without the need for a subsequent
Pull to retrieve the items.

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:

1. Add an optional element to the Enumerate request equivalent to
wsman:OptimizeEnumeration.

2. Add optional wsen:MaxTime, wsen:MaxElements, and wsen:MaxCharacters elements
to the wsen:Enumerate element. These elements must not appear unless the
“OptimizeEnumeration” element is also present. It may make sense to make these
elements children of the “OptimizeEnumeration” element to align the schema and
semantic optionalities.

3. Add optional wsen:Items and wsen:EndOfSequence elements to the
wsen:EnumerateResponse element. These elements must not appear unless the
consumer included “OptimizeEnumeration” in the corresponding Enumerate request.

4. Add wsen:TimedOut to the list of faults that may be generated by the
Enumerate request.

5. Add a parameter to the wsenu:DataSource assertion to indicate that an
endpoint supports the Optimized enumeration feature.

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

7. 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:56:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 28 April 2010 21:56:38 GMT