> -----Original Message-----
> From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de]
> Sent: maandag 20 november 2017 11:40
> To: email@example.com
> Subject: Re: Serf support in trunk
> +1 for pulling it unless someone steps forward.
> > Am 19.11.2017 um 12:49 schrieb Rainer Jung <rainer.j...@kippdata.de>:
> > While testing the 2.5.0 alpha candidate I noticed, that our optional use
> serf in mod_proxy and mpm_event is pretty outdated (so unmaintained):
> > - the serf API we use was only present in serf until version 0.3.1
What serf api are we talking about?
There shouldn't have been any changes to the public api withing 1.3.x... but
then around 1.3.0 the project wasn't an ASF project yet.
> > - in May 2010 it was changed inside serf and httpd does not support this
> newer API
> > - serf currently is now at version 1.3.9 (August 2016) providing stable
> There is still some basic maintenance activity in the serf project, for
> for supporting newer scons build tool versions or support for OpenSSL
> > I do not actually know what the serf support adds to httpd, it seems
> mostly some "SerfCluster" feature for mod_proxy. There's no docs and some
> comments in the code indicate the impl is not complete. SVN logs point to
> the same direction.
I have no idea why some things were duplicated for different http engines...
As httpd user I don't see why I want to use different configurations for
different engines, except for one knob that chooses the engine.
Mod_pagespeed (another serf consumer) is also trying to become an ASF
project... Not sure if there would be any interest in that project.