On Wed, 2002-12-04 at 14:55, Nicholas Riley wrote:
> How about creating a separate property namespace for binary properties
> then? Or a separate mechanism? Requiring that client developers
> somehow agree on a standard for encoding binary props seems like
> putting up -more- barriers, not less.
In the long run, I think that namespacing properties is a losing
proposition.
To be really useful and to interoperate, we need to know more than if a
chunk of data is binary or not. If we are going to have some metadata
on our metadata, we should take it to its logical conclusion and have a
way of attaching mime-type information to properties. That way a client
could at least theoretically do the right thing with the data --- like
pop up an image viewer when you ask to look at the PNG that you've put
in a property.
Even if binary properties are encoded in base64, the mime type should
still be embedded in the prop in some systematic way.
-JT
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 4 22:16:35 2002