You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Jim Jagielski <ji...@jagunet.com> on 2026/06/01 12:42:49 UTC
motorz
I've been spending the last month hacking away on motorz, and have an updated patch ready to apply to trunk.
TBH, it's been awhile since I've committed anything and the process has seemingly changed quite a bit, with CHANGES being now folded into a subdir, etc...
Have the developer/contributor guides been updated with the new process? If not, anyone willing and able to help hand-hold me thru the re-learning flow?
TIA
--
Jim
"We are havin' it large!"
Tony Harrison
Re: MotorZ in trunk
Posted by Jim Jagielski <ji...@jagunet.com>.
For those interesting in trying it out on 2.4.x:
https://gist.github.com/jimjag/a93acf3e1a90689c2d1aa0c178a7dabf
> On Jun 2, 2026, at 6:41 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>
> MotorZ is now in trunk, via r1934868.
>
> My goal was to have a simple, basic, and streamlined Async MPM which would be ideally suited for httpd as a reverse proxy (hence the playful name). It's been a plan of mine that once some cycles opened up, to spend those "free" cycles doing more work on the Proxy aspects, which has always been a draw for me.
>
> Because it is a "new" MPM, I made sure to spend time providing its own little test suite and ensuring that it works with the h2 pytest suite as well, which is where I found a nagging and insidious bug in mod_http2.
>
> Because I absolutely suck at explanations and "technical writing", I leveraged Claude to help write-up what was changed and why and how.
>
> My hope is that it will be something we can include in the next subsequent release for 2.4.
>
> Cheers.
> --
> Jim
> "We are havin' it large!"
> Tony Harrison
>
--
Jim
"This is an outrage!"
Tony Harrison
MotorZ in trunk
Posted by Jim Jagielski <ji...@jagunet.com>.
MotorZ is now in trunk, via r1934868.
My goal was to have a simple, basic, and streamlined Async MPM which would be ideally suited for httpd as a reverse proxy (hence the playful name). It's been a plan of mine that once some cycles opened up, to spend those "free" cycles doing more work on the Proxy aspects, which has always been a draw for me.
Because it is a "new" MPM, I made sure to spend time providing its own little test suite and ensuring that it works with the h2 pytest suite as well, which is where I found a nagging and insidious bug in mod_http2.
Because I absolutely suck at explanations and "technical writing", I leveraged Claude to help write-up what was changed and why and how.
My hope is that it will be something we can include in the next subsequent release for 2.4.
Cheers.
--
Jim
"We are havin' it large!"
Tony Harrison
Re: motorz
Posted by Ruediger Pluem <rp...@apache.org>.
On 6/1/26 2:57 PM, Eric Covener wrote:
> On Mon, Jun 1, 2026 at 8:43 AM Jim Jagielski <ji...@jagunet.com> wrote:
>>
>> I've been spending the last month hacking away on motorz, and have an updated patch ready to apply to trunk.
>>
>> TBH, it's been awhile since I've committed anything and the process has seemingly changed quite a bit, with CHANGES being now folded into a subdir, etc...
See https://svn.apache.org/viewvc/httpd/httpd/trunk/README.CHANGES?revision=1908150&view=markup for the background
>>
>> Have the developer/contributor guides been updated with the new process? If not, anyone willing and able to help hand-hold me thru the re-learning flow?
>
>
> Should not be anything different. CTR in trunk, then top-level STATUS
> in 2.4.x (unless motorz is called out as CTR?)
motorz is not in 2.4.x. I guess this will be a separate discussion after the patches are in trunk.
Regards
Rüdiger
Re: motorz
Posted by Eric Covener <co...@gmail.com>.
On Mon, Jun 1, 2026 at 8:43 AM Jim Jagielski <ji...@jagunet.com> wrote:
>
> I've been spending the last month hacking away on motorz, and have an updated patch ready to apply to trunk.
>
> TBH, it's been awhile since I've committed anything and the process has seemingly changed quite a bit, with CHANGES being now folded into a subdir, etc...
>
> Have the developer/contributor guides been updated with the new process? If not, anyone willing and able to help hand-hold me thru the re-learning flow?
Should not be anything different. CTR in trunk, then top-level STATUS
in 2.4.x (unless motorz is called out as CTR?)
You may be looking at the STATUS file in the PMC private repo.