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

Re: setting a convention for property values

From: Glenn A. Thompson <gthompson_at_cdr.net>
Date: 2002-12-05 01:06:00 CET

Hey,

Ben Collins-Sussman wrote:

>Karl Fogel <kfogel@newton.ch.collab.net> writes:
>
>
>
>>Peter Davis <peter@pdavis.cx> writes:
>>
>>
>>>How about:
>>>
>>> bin:* = Always binary
>>> [anything else, including svn:*] = Always text (UTF-8)
>>>
>>>
So Now I have a decoded blob. Now what is it? How do I tell my client
what it is?
I like the previously mentioned:

bin:DoHickey
Content-Type: application/octet-stream
Content-Transfer-Encoding: base64
AAAAdGhpcyBpcyBhIHRlc3QK

People see/use this kind of stuff all the time in e-mail.

It also allows non-SVN savvy programs or shell scripting languages to
create property files which can be fed to svn via -F arguments.

As for the Repos. Well it might be nice to formalize the "Content-xxxx
:" name value pairs. But some crazy FS/Repos implementor could parse
the headers for "bin" properties and store the meta-meta data however
they see fit. Or if additional Property methods are wanted/need
(i.e. getPropHeader()) and the data is stored as a single header + blob
string, parse the header at retrival time to get the required info to
support the new method(s).

Or perhaps a flag on propget that indicates headers only. This flag
would only apply to bin properties. So proplist --verbose would list
only the header for binary properties and the actual property for txt
properties.

OR configurable header filters, validators ....... Ummmm Sounds like
fun to me:-)

gat imposter (Real gat off working.)

 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 5 01:05:20 2002

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