The biggest benefit of gstein's approach would be that it works even
for very old servers. A very strong argument if serf would be the new
The only other valid option would be to implement the fetch-all, like
Ivan suggested. That would also perform well on current servers.
We can't assume users have 1.8 servers the day 1.8 is released :(
And if we could, we could assume editor v2.
Bert Huijben (Cell phone)
From: Justin Erenkrantz
Sent: 19-5-2012 21:21
To: Ivan Zhakov
Cc: C. Michael Pilato; Greg Stein; dev_at_subversion.apache.org
Subject: Re: [DISCUSS] delete ra_neon
On Sat, May 19, 2012 at 10:34 AM, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
> 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.
If you do that, then you have to store all of the properties in-memory
for the entire checkout or serialize on to disk or something
I'd also be curious how much extra time it takes to include the
properties in the REPORT response - it's not going to be free and may
not even be cheap. =( -- justin
Received on 2012-05-19 21:28:51 CEST