I had a question after reading Philip's pointer to the past discussion
about text vs. binary properties. I would think that a relatively simple
(depends on current implementation, sure) thing to do would be
to change <name,value> to <name,type,value>.
propset could default the type to text/plain;charset=utf-8 for all
properties
unless a --mime-type option is used. That should address the compatability
issues with text. Users who want to store binary files that aren't a
mime-type
would still have a place to give some type or endian-ness or whatever.
It seems that the only concern with this approach previously
mentioned was the redundancy in the type storage, but I'd rather have
redundancy with disk space costing what it does than go the whole
inheritance route <*shudder*>.
I think one problem with this would be if someone wanted to set a text
property
that wasn't UTF8, but that probably should fall under the policy of
enforcing a standard for compatability purposes.
Hmm. I'd go ahead and try to make a patch for this, but the school quarter
isn't over yet, I have my class project to finish up, etc., and maybe y'all
have something to say about my "relatively simple" assumption.
-Jen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 2 19:40:35 2003