[Bug 11990] New: Enum: MaxTime on create is problematic

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

           Summary: Enum: MaxTime on create is problematic
           Product: WS-Resource Access
           Version: PR
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Enumeration
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: dug@us.ibm.com
         QAContact: public-ws-resource-access-notifications@w3.org


Enum has this text for the MaxTime element:
- - - - -
The data source MUST recognize the wsen:MaxTime element and return a
wsen:TimedOut fault if no elements are available prior to the request message's
deadline. However, this fault MUST NOT cause the enumeration context to become
invalid and the consumer can issue additional Enumerate requests using this
enumeration context after receiving this fault. 
- - - - -

This is problematic due to the Pull() and Enumerate() now being
part of the same operation.  If the MaxTime is hit is during the
Enumerate/Create step a fault is thrown - this means that the client
will never get back the EnumerationContext for the new enum (which is still 
active). They would have no choice but to create an entirely new Enum - which
may not be what they want - and it means we have zombie enums left around.

Proposal:
- Modify Enum so that when MaxTime is hit the data source just returns
  zero Items in the response instead of a fault.
- remove the TimedOut fault
- modify the xsd so that Items can be empty

-- 
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 Sunday, 6 February 2011 13:07:02 UTC