I'm looking (again) at issue #1015, where we get binary properties to
work over DAV by base64-encoding anything that isn't XML-safe (and
using a different DAV namespace to indicate what we've done).
The upgrade plan for this to first get servers able to recognize the
new namespace, but disable binary property support in libsvn_ra_dav
(client-side). Then, after the supporting server code has been "out
there" a while, we enable client support.
The concern I have about this regards anyone who already has binary
properties in their repositories and switches to RA-DAV between the
time server support and client support are added. I suspect that the
result will be that the server base64-encodes those properties, and
some else { ... } block in the client will gladly drop that
base64-encoded value into a working copy as-is. Now we've got
properties out of sync between repos and working copy.
Now, there is no way that someone with binary properties could
*already* be using RA-DAV -- I mean, that's why issue #1015 exists.
So, perhaps we can just get away with announcing that folks with
binary properties in their repositories should *NOT* start using
RA-DAV until 0.25 or later (whenever it is that clients learn the
binary prop behavior).
Thoughts?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 10 22:35:28 2003