Garret Wilson wrote on Fri, Jan 20, 2012 at 10:38:28 -0800:
> From my end I'm actually starting with 100% canonically-encoded URIs
> to begin with. If Subversion is storing these things in decoded form
> on the back end, does it compensate for characters not supported by
> the underlying file system? So when I take my URI and I decode it
> just so I can save the filename the way Subversion likes, how do I
> know which characters to decode (those supported by the underlying
> file system---as if I, the client know what that is!) but which
> characters to leave encoded (those not supported by the underlying
> file system on the server)?
You don't care what FS backend the server runs. All you care is that
the endpoint of svn_ra_open4() implements the Subversion RA API
properly. Normal Subversion servers use svn_fs.h which in turn presents
the same API _regardless of which backend is used_.
I'll spell it out: the notion of 'valid pathname in a Subversion
filesystem' does not depend on the FS backend in use.
Received on 2012-01-21 03:15:17 CET