A few more comments below. Mostly, I think I understand you.
Thanks,
Joel
On 7/13/15 10:26 PM, Andy Bierman wrote:
On Mon, Jul 13, 2015 at 7:14 PM, Joel M. Halpern <[email protected]
<mailto:[email protected]>> wrote:
Andy, I am not following your comments. Questions in line below.
Joel
On 7/13/15 10:07 PM, Andy Bierman wrote:
On Mon, Jul 13, 2015 at 6:42 PM, Joel M. Halpern
<[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>> wrote:
The flexibility Jeff has described, and you have commented
upon, is
permitted but not required by (what I understand of) the
agreements
of the WG. If it can be easily done, it seems like a nice
thing to do.
It means the priority, client-ID, and 2nd-id all need to be
saved per
subtree.
per subtree? The client-ID needs to be saved with the changed node.
The secondary ID ought to be saved there, but is not required. If
we want to support variable priority, then we would need to record
the priority. Otherwise, recording the priority is an
implementation acceleration, as it is determinable from the client ID.
If the client creates a list entry then the priority applies to the list
node
and its descendants -- that's what I mean by subtree,
Okay.
Is the 2nd-id sticky?
If /foo is created with 2nd=app21 and it is updated later
with a new value, but no 2nd is provided, is the old 2nd
reported (as per traceability requirements doc?)
Or is the 2nd forgotten by the server as soon as it is logged?
So the update edit would have no 2nd-id (as the request specified)?
2nd ID is,as far as I can tell, per-operation.
If the Client does not send a second ID with a specific operation, then
the Agent will presume that there is no second ID. So the early second
ID (which was logged when the operation was performed) will be removed.
And will therefore not be included if a later error message is
generate. That is what the client has indicated by not including a
secondary ID on the operation.
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
