Re: [squid-dev] [RFC] Support concurrent SBuf::c_str() calls

2016-10-02 Thread Amos Jeffries
On 3/10/2016 1:03 p.m., Alex Rousskov wrote: > On 10/02/2016 03:25 PM, Kinkie wrote: >> On Fri, Sep 30, 2016 at 6:03 PM, Alex Rousskov >> wrote: >>> On 09/29/2016 09:19 PM, Amos Jeffries wrote: On 30/09/2016 5:03 a.m., Alex Rousskov wrote: > Should we

Re: [squid-dev] [PATCH] convert DNS shutdown to runner

2016-10-02 Thread Amos Jeffries
On 3/10/2016 1:29 p.m., Alex Rousskov wrote: > On 10/02/2016 06:35 AM, Amos Jeffries wrote: >> This patch adds a Runner to manage the DNS component state on shutdown >> (and the matching reconfigure port closures). The actions taken on >> reconfigure and shutdown are not changed, just their

Re: [squid-dev] [RFC] Support concurrent SBuf::c_str() calls

2016-10-02 Thread Alex Rousskov
On 10/02/2016 03:25 PM, Kinkie wrote: > On Fri, Sep 30, 2016 at 6:03 PM, Alex Rousskov > wrote: >> On 09/29/2016 09:19 PM, Amos Jeffries wrote: >>> On 30/09/2016 5:03 a.m., Alex Rousskov wrote: Should we remove the increment to make concurrent c_str() calls

Re: [squid-dev] [RFC] Support concurrent SBuf::c_str() calls

2016-10-02 Thread Kinkie
On Fri, Sep 30, 2016 at 6:03 PM, Alex Rousskov wrote: > On 09/29/2016 09:19 PM, Amos Jeffries wrote: >> On 30/09/2016 5:03 a.m., Alex Rousskov wrote: >>> Should we remove the increment to make concurrent c_str() calls safe? > >> The reason it exists remember is

[squid-dev] [PATCH] convert DNS shutdown to runner

2016-10-02 Thread Amos Jeffries
This patch adds a Runner to manage the DNS component state on shutdown (and the matching reconfigure port closures). The actions taken on reconfigure and shutdown are not changed, just their timing. Visible differences are now that Squid logs when DNS ports are being closed (and the reason), also