[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

more property thoughts

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-02-07 22:14:29 CET

Karl, I like the track you & Mike are on, regarding rewriting the way
properties exist on the client-side.

But I've got some bigger, broader issues.

Greg thinks we should stop categorizing props so much. RA->get_file
is going to return all 3 categories of props in a single hash. I plan
for the update-editor's change_file_prop() to stop categorizing as
well -- just cache the propchanges, let someone else sort them out.
Similarly, our new svn_wc_install_file() is going to be receiving a
single uncategorized list of properties.

That's all fine and well, but if we move to this new paradigm of 'a
proplist means *all* props', then we need to go -both- directions.
IOW, when we receive a proplist from the server, somebody eventually
ends up parsing the property namespaces and storing them in 3
different locations. But just as often, the merging process (and
other processes) require reading existing proplists from disk (for
comparisons, etc.) So we'll need a single 'read_proplist' routine
that will *suck* the data from 3 locations and combine them into one

Am I making sense?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:05 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.