Subversion efficiency while handling Zope Data.fs files?

Has anyone tried using subversion for backup and versioning Zope
Data.fs files? How efficient is this?

For those who do not know: Zope Data.fs file is usually fairly
large binary file (database of all the objects and scripts
making up the whole website) which in most cases is changed only
by appending small chunks of data at the end of the file. So
versioning Data.fs can mean scenario like: we have 50MB binary
file, 500 times a day something appends new 50, 100 or 500 bytes
at the end of it.

How efficient can be commit in such a scenario?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 14 16:32:16 2004