Re: Issue 908: Text-base compression status?

Lieven Govaerts <lgo@mobsol.be> writes:

> 3. Define a basic interface for reading & writing ( using streams presumably )

There is already a compressed stream interface in Subversion, although
nothing uses it. It has a design error (I think I am responsible) in
that it doesn't fail if the compression library is unavailable, in
retrospect I think it needs to fail.

> 4. Discuss the compression feature. Points to be raised:
> a. how can the user configure when to use compression? -> define all
> use-cases.
> - define for the whole working copy, or folders
> - limit compression to certain extensions only

Ideally the user would be able to specify it on a per wc and/or file
and/or extension, but we don't really have a mechanism to support that
yet. I'd keep things simple and just have a global enable/disable in
.subversion/config.

> b. where are these settings stored
> c. what's the abstraction level of the interface, what does the client code
> need to know about compression of the wc.
> d. how do we mark a file as compressed ( .gz/zip, in entries file, .zvn
> folder, svn-zbase etc. )

We deliberately use the .svn-base suffix so that the text-base files
don't look like working files, so that more-or-less rules out a .gz
suffix. I suppose a .svn-zbase suffix might work, but I suspect the
entries file would be better. I think either way will require an
increase in the wc version number.

> I'm not uptodate concerning other features that might have an impact on this
> one, so any input on that is appreciated.
> What would be the best branch to start with? I prefer to start from
> branches/1.2.x, or is it better to start from trunk?

Use the trunk, 1.2.x is bugfix only.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org