On Tue, 2014-05-13 at 11:56 +0100, Rob Elliot wrote: > On 13 May 2014 09:01, Oleg Kalnichevski <[email protected]> wrote: > > > > On Mon, 2014-05-12 at 13:48 +0100, Rob Elliot wrote: > > > > > > We're considering extending httpclient-cache to make [it cache the > responses > > > to HEAD requests], but we > > > don't want to lock ourselves out of upgrading forever. If we were to do > so > > > and offer to contribute it back to the project would you be interested? > > > > > > Regards, > > > Rob > > > > > > > The best course of action would be to raise a JIRA with a change request > > and attach propose changes as a patch in udiff format. Alternatively you > > might want to fork httpclient in github [1] and open a pull request with > > the project. > > > > Thanks, Oleg. Can I take it from this that you would be receptive to this > change? > It'd be good to know that, provided we implement it well, it would be > likely to be > accepted before we steam ahead and do it. > > Thanks, > Rob >
Rob, I generally try to stay away from anything cache related. I hope Jon or Francois-Xavier can comment whether or not the proposed change is likely to get accepted. Generally, a well engineered patch that comes with a decent test coverage is likely to get incorporated in one way or another. Even _if_ the whole idea got rejected we could still try to make the caching module extensible in such a way as to enable you to plug in some non-standard custom code to archive the desired effect without having to fork the framework. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
