On 6 April 2010 15:25, Robert Collins <email address hidden> wrote:
> We could make it richer yes; do we need that though?
I don't know but it seems possible. Some files are just about
guaranteed to be immutable once written, like pack files. Some are
modified but then otherwise cacheable, and in that case
must-revalidate would make sense.
At any rate I wouldn't want a proliferation of options on every single call.
Perhaps it should be per-transport state and then you can create
different transport objects. Or a dict of options per call.
On 6 April 2010 15:25, Robert Collins <email address hidden> wrote:
> We could make it richer yes; do we need that though?
I don't know but it seems possible. Some files are just about
guaranteed to be immutable once written, like pack files. Some are
modified but then otherwise cacheable, and in that case
must-revalidate would make sense.
At any rate I wouldn't want a proliferation of options on every single call.
Perhaps it should be per-transport state and then you can create
different transport objects. Or a dict of options per call.
-- launchpad. net/~mbp/>
Martin <http://