On Sat, May 19, 2012 at 10:15 AM, Justin Erenkrantz
> On Sat, May 19, 2012 at 7:09 AM, Bert Huijben <bert_at_qqmail.nl> wrote:
>> E.g. for directories we update the list of children and the properties in
>> one operation, to avoid the old 'incomplete' state of editor v1.
> Does that also mean the properties of all of the children as well?
Nope. Just the props/children of the directory. Once that has been
done, then the directory has been updated.
Children are updated separately.
When the new set of children is specified, we can create "incomplete"
child nodes for any new children. At some point in the future, they
will get added with their data. The children are otherwise ignored
(ie. we don't immediately delete any children; we wait for a delete())
> If so, this may be why Greg has suggested a PROPFIND Depth: 1 call as
> that'll mesh with the Ev2 semantics if that's the case.
Nope. Just as a mechanism for reducing traffic (due to HTTP
request/response overhead), and to reduce server CPU (fewer requests
Regarding the other stuff: there are no batched requests in Ev2,
today. And each node is updated in a single call, as Bert indicated.
File handles should not be a problem since you do one of:
add_directory(path, contents, props)
alter_directory(path, contents, props)
So the file handle for 'contents' only needs to be open for the
duration of that call. Either one (but not both) may be NULL if only
one aspect will be altered. Two calls are not allowed for a given path
(eg. you can't set contents, then later set props).
Received on 2012-05-19 22:24:40 CEST