/brz/remove-bazaar

To get this branch, use:
bzr branch http://gegoxaren.bato24.eu/bzr/brz/remove-bazaar

« back to all changes in this revision

Viewing changes to doc/developers/groupcompress-design.txt

  • Committer: Robert Collins
  • Date: 2010-05-06 23:41:35 UTC
  • mto: This revision was merged to the branch mainline in revision 5223.
  • Revision ID: robertc@robertcollins.net-20100506234135-yivbzczw1sejxnxc
Lock methods on ``Tree``, ``Branch`` and ``Repository`` are now
expected to return an object which can be used to unlock them. This reduces
duplicate code when using cleanups. The previous 'tokens's returned by
``Branch.lock_write`` and ``Repository.lock_write`` are now attributes
on the result of the lock_write. ``repository.RepositoryWriteLockResult``
and ``branch.BranchWriteLockResult`` document this. (Robert Collins)

``log._get_info_for_log_files`` now takes an add_cleanup callable.
(Robert Collins)

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/groupcompress-design.txt
29
29
 
30
30
Reasonable sizes 'amount read' from remote machines to reconstruct an arbitrary
31
31
text: Reading 5MB for a 100K plain text is not a good trade off. Reading (say)
32
 
500K is probably acceptable. Reading ~100K is ideal. However, it's likely that
 
32
500K is probably acceptable. Reading ~100K is ideal. However, its likely that
33
33
some texts (e.g NEWS versions) can be stored for nearly-no space at all if we
34
34
are willing to have unbounded IO. Profiling to set a good heuristic will be
35
35
important. Also allowing users to choose to optimise for a server environment