Hello!
On 17/01/2019, 13:24, Maxim Dounin wrote:
>
>Sorry, I'm a bit busy with other tasks now. Hopefully I'll
>be able to look again at the patch later this month.
Just a gentle nudge regarding the "proxy cache lock" patch.
I’ve tested it out. The patch still applies to Nginx master and works a
Hello!
On Fri, Mar 15, 2019 at 10:23:15AM +, Thomas Peterson wrote:
> It's now been several months since you last responded to this patch - is
> there any particular action we can take to help move things along please?
I'm still busy with other tasks, sorry about that. A review by a
quali
Hi Max,
It's now been several months since you last responded to this patch - is
there any particular action we can take to help move things along please?
Regards
On 17/01/2019 13:24, Maxim Dounin wrote:
Hello!
On Wed, Jan 16, 2019 at 10:20:59AM +, Elliot Thomas wrote:
With regards t
Hello!
On Wed, Jan 16, 2019 at 10:20:59AM +, Elliot Thomas wrote:
> With regards to the cache locking on stale patch, are there any further
> improvements I should make?
Sorry, I'm a bit busy with other tasks now. Hopefully I'll
be able to look again at the patch later this month.
--
Max
Hello!
With regards to the cache locking on stale patch, are there any further
improvements I should make?
Regards,
Elliot
---
Please ignore the following disclaimer, it’s a bit silly.
I have read the contribution guide, and am fine with it.
-
http://www.bbc.co.uk
Hello!
On 10/12/2018, 19:07, "nginx-devel on behalf of Maxim Dounin"
wrote:
...
> Note that posting patches to a public mailing list with such a
> disclaimer might not be a good idea. If you cannot remove it,
> please make sure to add an explicit comment that you understand
> that you are post
Hello!
On Mon, Dec 03, 2018 at 12:11:15PM +, Elliot Thomas wrote:
> This patch applies cache locking behaviour to stale cache entries, so
> in the case where the *_cache_lock directives are used, the same
> locking behaviour is used for stale content as it is for new entries.
>
> Previousl
Hello,
This patch applies cache locking behaviour to stale cache entries, so
in the case where the *_cache_lock directives are used, the same
locking behaviour is used for stale content as it is for new entries.
Previously, this was only done for new cache entries.
(see: http://mailman.nginx.or
