Re: Scoreboard 3.0

On May 11, 2016 4:16 PM, "Eric Covener" wrote: > > On Wed, May 11, 2016 at 8:28 AM, Stefan Eissing > wrote: > > I got some such feedback when h2 connections truly went async and no longer showed up as occupying a slot. I share your idea that in an

bugzilla spam

Infra is aware and firefighting. -- Eric Covener cove...@gmail.com

Re: Scoreboard 3.0

On Wed, May 11, 2016 at 8:28 AM, Stefan Eissing wrote: > I got some such feedback when h2 connections truly went async and no longer > showed up as occupying a slot. I share your idea that in an event based > server, threads are not the primary dimension but

Re: Detecting client aborts and stream resets

Zitat von Stefan Eissing : Thanks for the patch! I applied it to trunk in r1743335, will be part of next 1.5.4 release. I only omitted the last change as I do not want to set aborted on the main connection every time the session closes. Ok, that's fine for me.

Re: Scoreboard 3.0

On Wed, May 11, 2016 at 10:28 AM, Stefan Eissing < stefan.eiss...@greenbytes.de> wrote: > > > Am 11.05.2016 um 17:03 schrieb William A Rowe Jr : > > > > It seems like a lot of the scoreboard confusion lies in the event > > MPM lies in the work-performed-by-thread model of the

Re: End of the road of 2.2.x maintenance?

> On 10 May 2016, at 21:38, William A Rowe Jr wrote: > > > Are we ready to start the 12 month countdown as of the next/final bug > fix release of 2.2, and highlight this in both the 2.2 and 2.4 announce > broadcasts? > > I'm hoping we conclude some fixes of 2.4 scoreboard

Re: End of the road of 2.2.x maintenance?

On 05/10/2016 10:38 PM, William A Rowe Jr wrote: > It's been a year, and seems to be a good time to revisit this topic > while those folks who are present at ApacheCon can discuss f2f > the merits of bringing the 2.2.x chapter to a close, and share their > thoughts back here on-list. > >

Re: Scoreboard 3.0

> Am 11.05.2016 um 17:03 schrieb William A Rowe Jr : > > It seems like a lot of the scoreboard confusion lies in the event > MPM lies in the work-performed-by-thread model of the thread > based scoreboard. > > Let's call this existing model 'ExtendedStatus threads' > >

Scoreboard 3.0

It seems like a lot of the scoreboard confusion lies in the event MPM lies in the work-performed-by-thread model of the thread based scoreboard. Let's call this existing model 'ExtendedStatus threads' What it seems some users and committers are looking for is a different model, let's call this

Re: svn commit: r1742794 - /httpd/httpd/branches/2.4.x/STATUS

On Tue, May 10, 2016 at 11:36 PM, William A Rowe Jr wrote: > On Tue, May 10, 2016 at 7:26 PM, Yann Ylavic wrote: > >> >> The case where this happens is for keepalive/lingering-close handling. >> Suppose thread t1 handles request r1 on connection c1,

Re: Detecting client aborts and stream resets

Thanks for the patch! I applied it to trunk in r1743335, will be part of next 1.5.4 release. I only omitted the last change as I do not want to set aborted on the main connection every time the session closes. Cheers, Stefan > Am 10.05.2016 um 14:37 schrieb Michael Kaufmann