LOL IF YOU THINK THE WAIT FOR ITHREAD SUPPORT WAS A LONG TIME COMING.
https://github.com/majorz/apache2-rs/tree/master/src
On Fri, Aug 26, 2022 at 2:36 PM John D Groenveld <groenveld@acm.org> wrote:
> In message <
> CAFQGv+YB4BO3K4_HRYCcyj7LjsnejRH9hWYJw+9172ybc+q4xQ@mail.gmail.com>
> , Joe Schaefer writes:
> >The entire collective engineering effort for mod_perl and mod_apreq was to
> >ensure our code was thread-safe, both from an httpd context and a Perl
> one.
> >We achieved that twenty years ago, but have been stuck dealing with the
> >fact that ithread engineering within Perl5 itself had a ways to go.
>
> My WAG is that new application development that requires instrumenting
> the Apache httpd request phases is now being coded in Rust.
>
> John
> groenveld@acm.org
>
--
Joe Schaefer, Ph.D.
We only build what you need built.
<joe@sunstarsys.com>
954.253.3732 <//954.253.3732>
https://github.com/majorz/apache2-rs/tree/master/src
On Fri, Aug 26, 2022 at 2:36 PM John D Groenveld <groenveld@acm.org> wrote:
> In message <
> CAFQGv+YB4BO3K4_HRYCcyj7LjsnejRH9hWYJw+9172ybc+q4xQ@mail.gmail.com>
> , Joe Schaefer writes:
> >The entire collective engineering effort for mod_perl and mod_apreq was to
> >ensure our code was thread-safe, both from an httpd context and a Perl
> one.
> >We achieved that twenty years ago, but have been stuck dealing with the
> >fact that ithread engineering within Perl5 itself had a ways to go.
>
> My WAG is that new application development that requires instrumenting
> the Apache httpd request phases is now being coded in Rust.
>
> John
> groenveld@acm.org
>
--
Joe Schaefer, Ph.D.
We only build what you need built.
<joe@sunstarsys.com>
954.253.3732 <//954.253.3732>