W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > June 2009

Re: [Bug 6956] Enum: server behavior after end of enumeration context reached

From: Doug Davis <dug@us.ibm.com>
Date: Thu, 11 Jun 2009 00:12:10 -0400
To: Geoff Bullen <Geoff.Bullen@microsoft.com>
Cc: "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
Message-ID: <OF392DED33.97E26165-ON852575D2.0016A6F5-852575D2.00171834@us.ibm.com>
I guess the w3c mailing list removes the highlighting so I'm not sure of 
the exact bits that are new but this looks good to me.

(If this is accepted can you send me a direct note with the highlighting 
so it'll be easier for me to add it to the spec)

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.



Geoff Bullen <Geoff.Bullen@microsoft.com> 
Sent by: public-ws-resource-access-request@w3.org
06/10/2009 10:43 PM

To
"public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
cc

Subject
[Bug 6956] Enum: server behavior after end of enumeration context  reached






Here is my updated proposal for 6956.  Does this work better for people?
--Geoff
 
 
Current Proposal : 
 
section 3.2 (response) be changed to: ?MAY generate a
wsen:InvalidEnumerationContext message?, and delete the ?in any case, they 
MUST
NOT return a valid PullResponse?.
 
 
New Refined Proposal:
 
Changes are in yellow?
 
[Body]/wsen:Pull/wsen:EnumerationContext
 
This required element contains the XML data that represents the current 
enumeration context. 
 
The data source MUST fail the request and MUST generate the 
wsen:InvalidEnumerationContext fault if the data source is able to 
determine that the enumeration context is invalid for any reason 
including:
1.  Context replaced in the response to another Pull request
2.  Context completed (i.e. an EndOfSequence has been returned in a Pull 
response)
3.  Context released
4.  Context expired
 
Note that the data source may not be able to determine that an enumeration 
context is not valid, especially if all of the state associated with the 
enumeration is kept in the enumeration context and refreshed on every 
PullResponse.
 
 
[Body]/wsen:PullResponse/wsen:EndOfSequence 
This optional element indicates that no more elements are available from 
this enumeration. Additionally, once this element is returned in a Pull 
response message, subsequent Pull requests using that enumeration context 
MUST generate a wsen:InvalidEnumerationContext fault message, if the data 
source is able to determine that the enumeration context is no longer 
valid. 
 
 
-----Original Message-----
From: bugzilla@wiggum.w3.org [mailto:bugzilla@wiggum.w3.org] 
Sent: Tuesday, June 09, 2009 9:47 AM
To: Geoff Bullen
Subject: [Bug 6956] Enum: server behavior after end of enumeration context 
reached
 
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6956
 
 
 
 
 
--- Comment #2 from Robert Freund <bob@freunds.com>  2009-06-09 16:47:03 
---
Action on Geoff to refine proposal due 6/10
 
 
-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You reported the bug.
 
 
Received on Thursday, 11 June 2009 04:12:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:18:04 GMT