On Sat, May 19, 2012 at 8:12 PM, Justin Erenkrantz
<justin_at_erenkrantz.com> wrote:
> On Sat, May 19, 2012 at 8:15 AM, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
>> PROPFIND per directory has another problem: we have to save properties
>> for all children of directory in memory.
>
> This ultimately depends upon how Ev2 structures it - if we can't feed
> the editor with the properties until the individual children are
> processed, then yes, we have to stash it in memory (within the RA
> layer) until we process the nodes. However, if we can deliver all of
> the properties via Ev2 as soon as the PROPFIND response comes in, we
> don't have that concern - ultimately, that makes it libsvn_wc's issue
> about how to handle the atomicity/incompleteness issue - which I
> *think* would be far more solvable...but YMMV. -- justin
As far I know, Greg current approach is to make node operation atomic
and allow each node modified only in one call during the edit.
--
Ivan Zhakov
Received on 2012-05-19 18:20:19 CEST