On Sat, May 19, 2012 at 8:28 PM, Justin Erenkrantz
<justin_at_erenkrantz.com> wrote:
> On Sat, May 19, 2012 at 9:19 AM, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
>> 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.
>
> Yah, that seems to be the consensus. If that's the case, yes, you are
> right and we would have to store the properties in memory within
> ra_serf for all of the properties for every entry in a directory. So,
> the memory usage for larger directories could go up...but, it'd only
> be the properties not the fulltext content - so, it shouldn't be too
> awful, but it'll quite likely be noticeable. Depending upon how we do
> the request parallelization, it's possible we could have a bunch of
> directories in-flight further increasing the overhead as we'd have
> multiple PROPFIND responses for large directories sitting in memory
> waiting for their fulltext to arrive.
>
> My take is that'll be a fair tradeoff, but I'd be happy to hear what
> others think. -- justin
I'm still in favor to include properties in update REPORT (Mike's
approach). PROPFINDs are not cached by proxies and working copy. There
are relatively small, so there is no real benefit to fetch them using
separate request.
--
Ivan Zhakov
Received on 2012-05-19 19:35:46 CEST