Good day, It was suggested that the mod_http3 feature be consolidated in server/mpm_common.c to reduce code duplication.
I have packaged the implementation into a single commit (+113, -2) targeting 2.5.x (trunk), which should make the proposed changes much easier to review: https://github.com/machine-moon/httpd/commit/5075bbf8d134c86b692a4a4b8d835bba88d6634d A backport to 2.4.x would also be trivial with this common approach. Concerns: - Does adding this to mpm_common.c mean that every MPM is expected to support it? NetWare and OS/2 appear feasible, but from my initial review mpm_simple does not. - If this lives in mpm_common.c and is expected to be supported by all relevant MPMs, the MPM functions may not need to be optional. As Graham suggested, a hook-based approach may be more appropriate. Discussion is also welcome on the pull request: https://github.com/apache/httpd/pull/699 Regards, Tarek On Tue, Aug 25, 2026 at 7:28 AM Graham Leggett via dev <[email protected]> wrote: > On 24 Aug 2026, at 16:38, Helmut K. C. Tessarek <[email protected]> > wrote: > > > On 2026-08-18 02:06, Tarek wrote: > >> I propose retargeting PR #699 to the 2.4.x series as an enabling step, > while developing the broader design on 2.5.x. > > > > I would not touch 2.5.x at all. There is no 2.6 in sight and I believe > Stefan explained the hassle and all that comes with that trunk dev concept > pretty well. > > > > Nobody will run 2.5.x in production and nobody has time to backport h3 > stuff to 2.4. > > > > I suggest to develop h3 on the 2.4 branch (which means people can > actually run it in prod) and should 2.6 ever see the light of day in 15 or > so years, h3 has probably been superseeded by h4 or h5. > > To clarify how development works at httpd, we develop first on the trunk > branch (2.5/2.6), and once we've got that working, we then backport this to > v2.4. > > The vast majority of changes to v2.5/2.6 have been successfully back > ported to v2.4 because they have not required a change in backwards > compatibility. I don't see the changes to support mod_http3 being any > different. > > Please don't underestimate the importance that this project places on > stability. Changes only appear on v2.4 when they are ready, and they are > not going to break existing users. No one has time for a server that > suddenly breaks for no good reason, and we follow a process to make sure > that does not happen. > > Regards, > Graham > -- > >
