6409 2009-01-14 00:11:48 +0000 WS-Enumeration - optimize enumerate 2009-03-12 00:21:49 +0000 1 1 1 Unclassified WS-Resource Access Enumeration FPWD PC Windows XP CLOSED WONTFIX http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jan/0017.html P2 normal --- 1 dug dug bob public-ws-resource-access-notifications oldest_to_newest 23055 0 dug 2009-01-14 00:11:48 +0000 As an optimization it would be nice if the client could ask for the first chunk of data (from the first Pull()) to be returned within EnumerateResponse message. Proposal: Add a new wsen:Pull element as a child of wsen:Enumerate in the Enumerate request: <wsen:Enumerate ?> <wsen:EndTo>endpoint-reference</wsen:EndTo> ? <wsen:Expires>[xs:dateTime | xs:duration]</wsen:Expires> ? <wsen:Filter Dialect="xs:anyURI"?> xs:any </wsen:Filter> ? <wsen:Pull> <wsen:MaxTime>xs:duration</wsen:MaxTime> ? <wsen:MaxElements>xs:long</wsen:MaxElements> ? <wsen:MaxCharacters>xs:long</wsen:MaxCharacters> ? </wsen:Pull> ? ? </wsen:Enumerate> /Pull basically the same as the Pull operation itself. If the data source is unable to satisfy this request then it MAY choose to ignore this element. and add wsen:Items and wsen:EndOfSequence to the EnumerateResponse: <wsen:EnumerateResponse ?> <wsen:Expires>[xs:dateTime | xs:duration]</wsen:Expires> ? <wsen:EnumerationContext>?</wsen:EnumerationContext> <wsen:Items> <xs:any> enumeration-specific element </xs:any> + </wsen:Items> ? <wsen:EndOfSequence/> ? ? </wsen:EnumerateResponse> /Items /EndOfSequence same as the Pull response stuff. 23105 1 bob 2009-01-15 01:00:45 +0000 defer until 2009-01-31 23141 2 dug 2009-01-16 11:16:14 +0000 Withdrawn