On Sun, 2007-11-25 at 13:58 +0000, vila wrote:
> There are no reliable ways to detect whether or not a proxy will behave
> correctly regarding caching so bzr will continue to use 'no-cache'
> directives.
>
> But we intend to make it more network-friendly by other means.
I think we should keep this open a bit longer.
Specifically, the current code assumes all files are equally hard to
cache. This is bogus.
e.g.
foo.knit: not safe to cache
foo.kndx: not safe to cache
branch.conf: not safe to cache
3847868641027641243.pack: safe to cache
3847868641027641243.iix: safe to cache
branch-format: safe to cache
format: safe to cache
lock/*: not safe to cache.
On Sun, 2007-11-25 at 13:58 +0000, vila wrote:
> There are no reliable ways to detect whether or not a proxy will behave
> correctly regarding caching so bzr will continue to use 'no-cache'
> directives.
>
> But we intend to make it more network-friendly by other means.
I think we should keep this open a bit longer.
Specifically, the current code assumes all files are equally hard to
cache. This is bogus.
e.g. 1243.pack: safe to cache 1243.iix: safe to cache
foo.knit: not safe to cache
foo.kndx: not safe to cache
branch.conf: not safe to cache
384786864102764
384786864102764
branch-format: safe to cache
format: safe to cache
lock/*: not safe to cache.
etc.
-Rob www.robertcolli ns.net/ keys.txt>.
--
GPG key available at: <http://