d *up* and became PMC chair.
On Sun, Feb 18, 2024 at 4:42 PM Joe Schaefer wrote:
> Would you trust any of them at this point?
>
> I have a copy of svn trunk. I will never use anything they release, no
> matter what they call it.
>
> Joe Schaefer, Ph.D.
> <https://suns
Would you trust any of them at this point?
I have a copy of svn trunk. I will never use anything they release, no
matter what they call it.
Joe Schaefer, Ph.D.
<https://sunstarsys.com/orion/features>
Orion - The Enterprise Jamstack Wiki <https://sunstarsys.com/orion/features>
2.18 will never be released. They are shutting down the project.
Joe Schaefer, Ph.D.
<https://sunstarsys.com/orion/features>
Orion - The Enterprise Jamstack Wiki <https://sunstarsys.com/orion/features>
954.253.3732
On Sun, Feb 18, 2024 at 4:32 PM Mithun Bhattacharya
wrote:
You are welcome, colleague!
Keep in mind the SoBs are threatening to release 2.18 as we speak, but like
everything else they do, it’s a dog and pony show in a Potemkin Village.
They simply are too lazy, inept, and mendacious to execute.
Use trunk, while it still exists.
Joe Schaefer, Ph.D
Trunk is the safe bet.
Joe Schaefer, Ph.D.
<https://sunstarsys.com/orion/features>
Orion - The Enterprise Jamstack Wiki <https://sunstarsys.com/orion/features>
954.253.3732
On Sun, Feb 18, 2024 at 2:11 PM Mithun Bhattacharya
wrote:
> So is there a cleaner/saner version of
.
Why do I care now? Because I’m the sucker users reach out to for answers as
a known subject matter expert.
This sucks, but I’m sorry to tell you that my days wearing the Superman
cape at Apache ended 8 years ago.
--
Joe Schaefer, Ph.D.
<https://sunstarsys.com/orion/features>
Orion - The Ente
In short, you should just be running Perl with the -T flag. Perl::Critic is
just a very opinionated linter.
Joe Schaefer, Ph.D
+1 (954) 253-3732
SunStar Systems, Inc.
Orion - The Enterprise Jamstack Wiki
From: Joseph He
Sent: Thursday, February 15, 2024 10:43
erl2 is an amazing solution that deserves a lot
> more publicity than it currently receives, and I'm optimistic about
> the future of it as I'm hearing lately that Perl is gaining more
> popularity again in recent years.
>
> > It´s not worth replumbing apr`s table API at t
dlers, you can always not use it.
On Wed, Feb 14, 2024 at 2:42 PM Ed Sabol wrote:
> On Feb 14, 2024, at 2:27 PM, Joe Schaefer wrote:
> > sealed.pm is really only necessary in a mod_perl context. And really it
> only matters if you are using subrequests to reenter :Sealed handlers.
&g
sealed.pm is really only necessary in a mod_perl context. And really it
only matters if you are using subrequests to reenter :Sealed handlers.
Otherwise I don't see the point of the exercise.
On Wed, Feb 14, 2024 at 2:25 PM Joe Schaefer wrote:
> Why would there be? It only impacts :sea
Why would there be? It only impacts :sealed subs, which is not bundled with
Perl.
On Wed, Feb 14, 2024 at 2:24 PM Ed Sabol wrote:
> On Feb 14, 2024, at 12:18 PM, Joe Schaefer wrote:
> > pad.c will segfault with an out-of-bounds memory access at line 2460 of
> pad.c.
>
> Is
pad.c will segfault with an out-of-bounds memory access at line 2460 of
pad.c. If you are willing to recompile perl with a dirty hotfix, there is
one mentioned near the bottom of this page:
https://blogs.sunstarsys.com/joe/perl7-sealed-lexicals.html.en.gz
--
Joe Schaefer, Ph.D.
<ht
It’s not worth replumbing apr‘s table API at this point.
Joe Schaefer, Ph.D.
<https://sunstarsys.com/orion/features>
Orion - The Enterprise Jamstack Wiki <https://sunstarsys.com/orion/features>
954.253.3732
On Wed, Feb 14, 2024 at 11:31 AM Randolf Richardson
wrote:
>
In short- No. All apreq interfaces use APR tables underneath.
On Wed, Feb 14, 2024 at 11:12 AM Randolf Richardson
wrote:
> Is there a way to use $r->param in a case-sensitive manner? The
> documentation indicates that keys are case-insensitive.
>
> Thanks.
>
> Randolf Richardso
We're making free tech blogs available to our social network on our
mod_perl + event_mpm platform.
Something like blogs.sunstarsys.com/joe look interesting? Get in on the
ground floor and contact me privately for your account.
Thanks! Let's revive the mod_perl tech community together
PerlInterpMaxRequests to be at least 10x greater than your
site's daily hit count.
3/ always disable the SetupEnv Option.
Yes, it's that simple. Any other core dumps are due to non-ithread-safe
3rd party Perl modules.
--
Joe Schaefer, Ph.D.
<https://sunstarsys.com/orion/features>
Orion
Nobody’s forcing you to use it.
Joe Schaefer, Ph.D
+1 (954) 253-3732
SunStar Systems, Inc.
Orion - The Enterprise Jamstack Wiki
From: Ed Sabol
Sent: Thursday, January 11, 2024 3:56:47 PM
To: mod_perl list
Cc: steve.m@googlemail.com
Subject: Re: Resolved
You need to build and install libapreq2.so from svn sources.
Joe Schaefer, Ph.D.
<https://sunstarsys.com/orion/features>
Orion - The Enterprise Jamstack Wiki <https://sunstarsys.com/orion/features>
954.253.3732
On Wed, Jan 10, 2024 at 5:21 PM Randolf Richardson
wrote:
>
mance efficiency boosts in your modperl handlers
with sealed.pm, (but avoid reentrancy/recursion for those subs, or you may
segfault).
--
Joe Schaefer, Ph.D.
<https://sunstarsys.com/orion/features>
Orion - The Enterprise Jamstack Wiki <https://sunstarsys.com/orion/features>
954.253.3732
Bien à vous, Vincent Veyron
>
> https://marica.fr/
> Logiciel de suivi des contentieux juridiques, des sinistres d'assurance et
> des contrats
>
> --
Joe Schaefer, Ph.D.
<https://sunstarsys.com/orion/features>
Orion - The Enterprise Jamstack Wiki <https://sunstarsys.com/orion/features>
954.253.3732
It’s a general purpose module, so it will enhance performance even outside
modperl apps.
Joe Schaefer, Ph.D
+1 (954) 253-3732
SunStar Systems, Inc.
Orion - The Enterprise Jamstack Wiki
From: Thomas den Braber
Sent: Wednesday, May 10, 2023 8:49:13 AM
To: j
the speed
bump on your core loops with OO-method calls in them.
Joe Schaefer, Ph.D.
< <mailto:j...@sunstarsys.com> j...@sunstarsys.com>
954.253.3732
<https://sunstarsys.com/orion/features> Orion - The Enterprise Jamstack
WikiT
Feedback/flames welcome. Am I beating a dead horse with mod_perl +
> > mpm_event in 2022?
> >
>
> --
> Henry R
> https://openmbox.net/
>
--
Joe Schaefer, Ph.D.
We only build what you need built.
954.253.3732
Includes ModPerl::RegistryCookerSealed which will monkey-patch your
ModPerl::Registry runtime to use :Sealed handlers for your registry scripts.
Feedback/flames welcome. Am I beating a dead horse with mod_perl + mpm_event
in 2022?
Joe Schaefer, Ph.D.
mailto:j...@sunstarsys.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Sorry the test script is for the cms build here:
https://github.com/SunStarSys/cms/blob/master/test.sh
- --
Joe Schaefer, Ph.D.
We only build what you need built.
954.253.3732
On 2022-09-17 at 17:48, j...@sunstarsys.com wrote:
> Be sure to p
Be sure to pick up the latest CPAN release of sealed.pm if you want to be able
to run this test script successfully:
https://github.com/SunStarSys/sealed/blob/master/test.sh
Joe Schaefer, Ph.D.
mailto:j...@sunstarsys.com> >
954.253.3732
SunStar Systems CMS <https://sunst
/joesuf4/home/blob/wsl/.zshenv
Joe Schaefer, Ph.D.
mailto:j...@sunstarsys.com> >
954.253.3732
SunStar Systems CMS <https://sunstarsys.com/CMS/> - The Original Markdown JAM
Stack™
openpgp-digital-signature.asc
Description: PGP signature
l::Registry script.
>
>
>
--
Joe Schaefer, Ph.D.
We only build what you need built.
954.253.3732
New project home dedicated to sealed.pm maintenance is at
https://github.com/SunStarSys/sealed
In the interest of saving more time and hassle, I put the best version I could
come up with on CPAN, so you don’t need to clone the repository unless you want
to benchmark the enquiry.pl ModPerl::Regi
1, 2022 at 8:11 PM Joe Schaefer wrote:
> 4.0.1 is going to trap everything bizarre that occurs within the tweak()
> subroutine, and gracefully bail out.
> The only thing this needs your help with is to avoid putting heavy ithread
> pressure on mod_perl during interpreter
> destruct
interpreter
settings never destroy ithreads-
leave that for httpd during graceful restart.
On Wed, Aug 31, 2022 at 7:41 PM Joe Schaefer wrote:
> To throw mod_apreq2 into the benchmarking mix, add items to the query
> string you are hitting (on enquiry.pl).
> In particular, lang=.{en,es,de
To throw mod_apreq2 into the benchmarking mix, add items to the query
string you are hitting (on enquiry.pl).
In particular, lang=.{en,es,de,fr} will generate UTF-8 European-language
localized output.
On Wed, Aug 31, 2022 at 7:13 PM Joe Schaefer wrote:
> I went ahead and copied my comp
I went ahead and copied my company templates over to the github cms repo,
so you can run enquiry.pl yourself
(once you edit the @TEMPLATE_DIRS path to point at your checkout). You
will see sealed.pm at work in the
httpd error logs.
On Wed, Aug 31, 2022 at 1:02 PM Joe Schaefer wrote:
> For
out the idea of putting sealed.pm into the modperl
project, vs. a stand-alone on CPAN?
On Wed, Aug 31, 2022 at 10:53 AM Joe Schaefer wrote:
> In the end, the surgery we do (to method_named), is to replace the prior
> $op's next() pointer to point at the $gv op we copied from
> a known su
*100_000 simultaneous requests.
On Wed, Aug 31, 2022 at 12:41 PM Joe Schaefer wrote:
> To explain the new-new here, with HTTP/2 comes this whole new idea of
> multiplexed "HTTP channels" within a single TCP connection. In this
> benchmark, each of the 1000 concurrent tcp
5.76s 3.09s58.62%
>
> time for connect:15.40ms212.74ms 62.57ms 54.73ms87.50%
>
> time to 1st byte: 261.01ms 9.04s 3.00s 2.01s68.00%
>
> req/s : 8.70 68.06 15.649.7385.70%
>
>
>
>
>
--
Joe Schaefer, Ph.D.
We only build what you need built.
954.253.3732
this tree (eg
B::Deparse) post-tweaks may choke on the zombie method_named
op lying around in one of the sibling() linked lists. That probably
includes the ithread-cloniing mechanism itself, so only use :sealed
post ithread construction, not prior to it.
On Wed, Aug 31, 2022 at 10:27 AM Joe Schae
for :sealed.
My advice that it's only practical to seal XS method calls remains.
On Wed, Aug 31, 2022 at 9:52 AM Joe Schaefer wrote:
> Submitted a Pull Request for the Generate.xs patch:
> https://github.com/rurban/b-generate/pull/2
> Added more comments to sealed.pm to explain the
Submitted a Pull Request for the Generate.xs patch:
https://github.com/rurban/b-generate/pull/2
Added more comments to sealed.pm to explain the rationale behind the #
replace $methop logic,
since it differs from what Doug did back in 2000.
On Tue, Aug 30, 2022 at 2:52 PM Joe Schaefer wrote
should this piece of the mod_perl puzzle fit in to
the CPAN universe?
On Tue, Aug 30, 2022 at 2:12 PM Joe Schaefer wrote:
> Every method call that's implemented in XS is looked-up at compile-time in
> that script, even for class methods.
> That's the sweet spot for :sealed. The on
0, 2022 at 1:14 PM Joe Schaefer wrote:
> Just look through my commit history on this sample Registry script to see
> what's involved in getting sealed activated on your scripts.
>
> https://github.com/SunStarSys/cms/blob/master/enquiry.pl
>
> On Tue, Aug 30, 2022 at 1:1
Just look through my commit history on this sample Registry script to see
what's involved in getting sealed activated on your scripts.
https://github.com/SunStarSys/cms/blob/master/enquiry.pl
On Tue, Aug 30, 2022 at 1:12 PM Joe Schaefer wrote:
> It'd be pretty harmless
n Tue, Aug 30, 2022 at 12:53 PM Joe Schaefer wrote:
> If you really beat the hell out of it thread-wise, sealed.pm v4.0.0 will
> still segfault, but there's not much more I can do with the code at this
> point to prevent that.
> B::Generate doesn't really support wha
the
feature were never resolved, because nobody wants to change the default
"virtual method"
behavior of Perl's OO-runtime-lookups. Now with the new :sealed SUBROUTINE
ATTRIBUTE, it's only enabled for people (like us) who want it conditionally
applied,
just like we do for the :meth
uot;,
$nph,
$shebang,
On Mon, Aug 29, 2022 at 2:21 PM Joe Schaefer wrote:
> Forgive me for the pent up frustration of having our wonderful mod_perl
> project being completely ignored and abandoned by the Perl Steering
> Committee's frivolous l
h2load -n 10 -c 1000 -m 100 http://localhost/perl-script/enquiry.pl
starting benchmark...
spawning thread #0: 1000 total client(s). 10 total requests
Application protocol: h2c
progress: 10% done
progress: 20% done
progress: 30% done
progress: 40% done
progress: 50% done
progress: 6
at they do with
it.
On Mon, Aug 29, 2022 at 1:34 PM Joe Schaefer wrote:
> If the Perl steering committee had any brains left it would have
> capitalized on the perl 5.34 release and Co announced modperl2 ithread
> compatibility now available with Perl7’s new release.
>
> Instead t
any more.
Get Outlook for iOS<https://aka.ms/o0ukef>
From: Joe Schaefer
Sent: Monday, August 29, 2022 1:17:17 PM
To: mod_perl list
Subject: Re: sealed.pm v4.0.0 is out
The only reason I’ve been vacillating about glibc/malloc thread safety is
because I co
was
corrupting the heap in some other part of the codebase, and there’s no simple
way to track it down without a tool like Valgrind, but we weren’t successful
with that effort either.
Get Outlook for iOS<https://aka.ms/o0ukef>
From: Joe Schaefer
Sent:
Religiously avoid setting up per request ithread environment variables. Just
use PerlSetEnv in your Webserver config. Everything we did in modperl to
support CGI scripts is a train wreck.
Get Outlook for iOS<https://aka.ms/o0ukef>
From: Joe Schaefer
kef>
From: Joe Schaefer
Sent: Monday, August 29, 2022 12:57:14 PM
To: mod_perl list
Subject: Re: sealed.pm v4.0.0 is out
The only impact to your work with modperl is that you will need to assess the
ithread-safety of your dependent XS-based modules. For example, use a JSON::XS
The only impact to your work with modperl is that you will need to assess the
ithread-safety of your dependent XS-based modules. For example, use a JSON::XS
thread safe alternative- there are several.
Get Outlook for iOS<https://aka.ms/o0ukef>
Fro
kef>
From: Joe Schaefer
Sent: Monday, August 29, 2022 12:40:43 PM
To: mod_perl list
Subject: Re: sealed.pm v4.0.0 is out
Many of the performance hacks we’ve encouraged over the years, eg around
HTTPD’s lingering close effect, are obsoleted with ithreads. Unle
blocking
socket system calls. So you need an order of magnitude fewer ithreads than you
do prefork children in a multitier arch.
Get Outlook for iOS<https://aka.ms/o0ukef>
From: Joe Schaefer
Sent: Sunday, August 28, 2022 11:09:14 AM
To: mod_perl list
Subje
ning mpm_event+mod_perl with a Network
> (TCP-level) Load Balancer in the front.
>
--
Joe Schaefer, Ph.D.
We only build what you need built.
954.253.3732
46387 1.7 1.5 7549352 129692 ? Sl 11:28 0:12
> /usr/sbin/apache2 -k start
>
> USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
>
> www-data 451006 15.2 1.5 7483708 128468 ? Sl 11:39 0:10
> /usr/sbin/apache2 -k start
>
> USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
>
> www-data 451317 11.7 1.4 7483772 119836 ? Sl 11:39 0:07
> /usr/sbin/apache2 -k start
>
> USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
>
> www-data 451629 6.4 1.3 7483804 113012 ? Sl 11:39 0:03
> /usr/sbin/apache2 -k start
>
> USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
>
> www-data 451929 1.1 1.4 7483816 116668 ? Sl 11:39 0:00
> /usr/sbin/apache2 -k start
>
--
Joe Schaefer, Ph.D.
We only build what you need built.
954.253.3732
There is an emerging industry trend towards consolidation an integration of
webstack technology, and mod_perl + mpm_event is well-positioned to eat
everyone else’s lunch in this space. The only real reason fastcgi-like
frameworks won out over the past two decades is because threading was/is cra
ery regime. The real tuning effort is to balance mpm_event
threads (100 - 1000x)
and ithreads.
- --
Joe Schaefer, Ph.D.
We only build what you need built.
954.253.3732
On 2022-08-27 at 15:42, j...@sunstarsys.com wrote:
> See https://sunstarsys.com/essays/perl7-sealed-lexicals. For the full
effec
See https://sunstarsys.com/essays/perl7-sealed-lexicals. For the full effect,
you will need to build B::Generate with this patched version instead:
https://github.com/SunStarSys/cms/blob/master/Generate.xs
Sample mod_perl config + benchmarks:
StartServers 2
I have a v4.0.0 beta for sealed.pm that I expect will be fully operational
with mod_perl+ithreads now, but I will let it soak for a week to see what
happens in prod.
On Fri, Aug 26, 2022 at 3:30 PM Joe Schaefer wrote:
> You're welcome. Pardon my rudeness, but you will understand whe
> On Aug 26, 2022, at 1:16 PM, Joe Schaefer wrote:
> > AFAICT you guys are just too lazy to look.
>
> That came across as rude, Joe. Not all of us are experts at Perl internals
> or track the latest changes to Perl's ithread support and/or glibc, and
> it's gen
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 wrote:
> In message <
> cafqgv+yb4bo3k4_hryccyj7ljsnejrh9hwyjw+9172ybc+q...@mail.gmail.com>
> , Joe
All of the zero-copy design elements of httpd are expanded on within
mod_perl in an ithread context.
All of those performance optimizations are lost when you bury them behind a
mod_proxy gateway to your application server running prefork.
Moreover, your scaling model for your application server is
with minimal memory footprint.
On Fri, Aug 26, 2022 at 1:49 PM Joe Schaefer wrote:
> Why are you still paying attention to mod_perl development, if you don't
> even care to use it to full effect?
> Running a 2-tiered webserver architecture is anathema to mod_perl. It's
> n
Groenveld wrote:
> In message zhwww5d7fcmmcgpdmxs...@mail.gmail.com>
> , Joe Schaefer writes:
> >Lazy enough never to support HTTP/2?
>
> If HTTP/2 becomes necessary, my lazy first answer is to enable it in my
> mod_proxy front end.
>
> John
> groenv...@acm.org
>
There isn't anything else on the market that will ever touch mod_perl +
mpm_event in terms of HTTP/2 performance.
And you don't need to ever spin up more ithreads than you have vCPU cores.
On Fri, Aug 26, 2022 at 1:36 PM Joe Schaefer wrote:
> Lazy enough never to support HTTP/2?
&g
Lazy enough never to support HTTP/2?
On Fri, Aug 26, 2022 at 1:32 PM John D Groenveld wrote:
> In message <
> cafqgv+btwpyvvup2ewzfn7ruv4sfgdihadh48cm3n8qxpwb...@mail.gmail.com>
> , Joe Schaefer writes:
> >AFAICT you guys are just too lazy to look. Running latest on CPA
work on the
5.22+ line.
On Wed, Aug 24, 2022 at 11:08 PM Joe Schaefer wrote:
> Has anybody actually tried running bleadperl with modperl and mpm_event on
> Linux? I wouldn’t be surprised if it works without coring in malloc() at
> this point, or at least can be tuned to work.
>
>
Has anybody actually tried running bleadperl with modperl and mpm_event on
Linux? I wouldn’t be surprised if it works without coring in malloc() at
this point, or at least can be tuned to work.
On Sat, Aug 20, 2022 at 11:31 AM Joe Schaefer wrote:
> Solaris libc malloc() is also tunable (%
Solaris libc malloc() is also tunable (% man mallopt again), but I can tell
you that I've yet to have a reason to bother, because it simply doesn't
dump core on my mod_perl applications.
On Sat, Aug 20, 2022 at 10:37 AM Joe Schaefer wrote:
>
>
> -- Forwarded messa
-- Forwarded message -
From: Joe Schaefer
Date: Fri, Aug 19, 2022 at 10:37 PM
Subject: Re: Experience running mod_perl2 with mpm_event on Solaris 11
To: pengyh
Seriously it’s always been a quality of implementation issue in open source
libc implementations (FreeBSD libc isn’t
.
> do you know what's the difference between them?
> I never heard people using mod_python to make some jobs.
>
> Thanks
>
--
Joe Schaefer, Ph.D.
We only build what you need built.
954.253.3732
Segfaults in glibc malloc should be reported to glibc developers. Not
here. There’s nothing we can do about it other than to suggest Solaris for
high performance modperl shops.
On Fri, Aug 19, 2022 at 9:28 PM Joe Schaefer wrote:
> My pleasure. Nobody’s going to fix this from the modp
My pleasure. Nobody’s going to fix this from the modperl developer side.
We don’t care any more. That ship sailed 20 years ago. I don’t think it’s
ever not worked on Solaris, so you get what you pay for in the end.
On Fri, Aug 19, 2022 at 9:25 PM Edward J. Sabol
wrote:
> Very interesting,
The problem is really confined to embedded uses of ithreads, because Perl
itself will mutex-wrap the malloc calls. In httpd, so do all apr_pool_t calls
to malloc. It's when the two memory management techniques are interacting that
there is no application-level way to guard against thread conte
I discuss different Dynamic Programming Language thread support at
https://sunstarsys.com/CMS/technology. The people in the Perl community at
large who knock Perl5's ithreads support are doing nobody any favors.
-Original Message-
From: Edward J. Sabol
Sent: Tuesday, August 16, 2022 2
Whatever you do, do not use Perl's sbrk-based malloc implementation. It's a
disaster with ithreads.
-Original Message-
From: Edward J. Sabol
Sent: Tuesday, August 16, 2022 2:27 PM
To: mod_perl list
Subject: Re: Experience running mod_perl2 with mpm_event on Solaris 11
On Aug 16, 2022
.@sunstarsys.com wrote:
> > To the best of my knowledge, the underlying problem with
> mod_perl+ithread is that it requires a reentrant malloc in libc.
>
> That's it? This is the first I'm learning this. Is there an option to
> compile Perl and mod_perl with a reentrant malloc on Linux?
>
> Thanks,
> Ed
>
--
Joe Schaefer, Ph.D.
954.253.3732
We've been plagued by endless Segmentation Faults on non-Solaris systems, where
the backtrace indicated the problem was in mod_perl -> Perl Code -> malloc (at
the top of the frame). For a while I thought p5p fixed this in 5.30+ releases,
but since nobody confirmed that suspicion I think the pro
Benchmarks from last year (based on openoffice.org):
https://www.youtube.com/watch?v=xr67QX6aMqU
From: j...@sunstarsys.com
Sent: Tuesday, August 16, 2022 12:31 PM
To: modperl@perl.apache.org
Subject: RE: :Sealed subs for typed lexicals
The build flags for Perl that I’m using on Solaris 1
underlying problem with mod_perl+ithread is
that it requires a reentrant malloc in libc. I haven’t tested modern Perl
releases against Linux/FreeBSD, but Solaris 11 is rock solid with ithreads and
event_mpm.
From: Joe Schaefer mailto:j...@sunstarsys.com> >
Sent: Tuesday, August 16, 2022 12
The build flags for Perl that I’m using on Solaris 11 are documented in the
sealed.pm source code linked to from that webpage.
From: j...@sunstarsys.com
Sent: Tuesday, August 16, 2022 11:13 AM
To: modperl@perl.apache.org
Subject: :Sealed subs for typed lexicals
Here’s some more fun I’ve
To the best of my knowledge, the underlying problem with mod_perl+ithread is
that it requires a reentrant malloc in libc. I haven’t tested modern Perl
releases against Linux/FreeBSD, but Solaris 11 is rock solid with ithreads and
event_mpm.
From: Joe Schaefer
Sent: Tuesday, August 16
Here’s some more fun I’ve been grinding out for the mod_perl community.
Unfortunately I haven’t resolved all the issues with using this stuff in a
mod_perl+ithread runtime, but if you figure out the right incantation please
let me know:
https://sunstarsys.com/essays/perl7-sealed-lexicals
The build system for the CMS is on GitHub here:
https://github.com/SunStarSys/cms. Full site builds clock in at around 500
MB/s on modern hardware (NVMe + 8 cores). But the real beauty is the
Incremental Build Support in the product itself, so you only build what you
changed.
From: Joe
You can read about it in the URL below, but I’ve had it running for over
two years as the linchpin of a Perl-based CMS that The ASF used to use
itself (under prefork).
It screams under HTTP2.
See
https://sunstarsys.com/CMS/
--
Joe Schaefer, Ph.D.
954.253.3732
CVE-2019-12412: libapreq2 null pointer dereference
Severity: important
Vendor: The Apache Software Foundation
Versions Affected:
libapreq2 2.07 to 2.13
Description:
In libapreq2 versions 2.07 through 2.13 inclusive, a flaw in the
multipart parser can deference a null pointer leading to a proce
libapreq2-2.15 Released
The Apache Software Foundation and The Apache HTTP Server Project
are pleased to announce the 2.15 release of libapreq2. This
Announcement notes significant changes introduced by this release.
libapreq2-2.15 is released under the Apache License
version 2.0. It is
3a1ac2086eb
> SHA1 = 17aa9a8669023aa2f485aa83f8f389969b8e5f0c
I can't remember if I'm a PMC member for perl.a.o but +1 for release
from me, this looks good to me.
Regards, Joe
+1, nice job Steve!
On Wednesday, May 13, 2015 6:52 PM, David E. Wheeler
wrote:
On May 13, 2015, at 1:40 PM, Steve Hay wrote:
>> http://people.apache.org/~stevehay/mod_perl-2.0.9-rc1.tar.gz
>>
>
> If I can vote for my own RC then it's a +1 from me :-)
Tested builds on CentOS 6
this code in httpd.h:
> >>>
> >>> #ifdef AP_DEBUG
> >>>
> >>> #undef strchr
> >>> # define strchr(s, c) ap_strchr(s,c)
> >>> #undef strrchr
> >>> # define strrchr(s, c) ap_strrchr(s,c)
> >>> #undef strstr
>
On Thursday, April 2, 2015 6:21 PM, Joe Schaefer
wrote:
Bio-Tech Medical Software Inc. is expanding its South Florida HQ and is
looking to grow its small but skilled IT department to meet expected market
demand for our products. Our subsidiary, BioTrackTHC, provides market
apreq validates anything it presents as utf8, otherwise it marks it as ISO88591
or some windows encoding I don't remember the name of if that fails.
On Monday, September 8, 2014 3:17 PM, André Warnier wrote:
Michael Schout wrote:
> On 9/2/14, 4:19 PM, Randal L. Schwartz wrote:
>
>> ##
et?
My server provider is installing the apahce + perl etc. so
I'm partly at their mercy to get it correct. I just had no verified
test cases that I could say to them: This *should* work if the installation
is correct...
Thanks agains,
Joe N
##
package respHandler;
use strict;
?
Ideally a simple one module working code response handler that illustrates
access to the
parsed request, handles args as querystrings and Post data, uploads a file or
two, and returns an html page to the requestor. Anyone have something like that?
Thanks very much in advance,
Joe N
apreq has clean handling of chunked POST data. You might start
there.
- Original Message -
> From: Raf
> To: modperl@perl.apache.org
> Cc:
> Sent: Monday, July 16, 2012 8:13 AM
> Subject: Mod-perl handling of Chunked POST's
>
>
> I am using Plack::Handler::Apache2 to dispatch to a c
e timing issues here,
so buyer beware. My point still stands: interrupt the POST
prior to sending the Continue, not afterwards.
- Original Message -
> From: Joe Schaefer
> To: Vincent Veyron ; mike cardeiro
> Cc: Torsten Förtsch ; "modperl@perl.apache.org"
>
&
I don't think people groked my point very well. When you POST
via HTTP/1.1, httpd will send a "Continue: 100" header before it
starts doing blocking reads on the client socket (any attempts to
read from the client will trigger this behavior). If you really
want to interrupt an upload, the time to
You probably don't want to do this with a hook if you can
avoid it. The reason is that once httpd sends the 100 Continue
it will read the entire upload, even after CGI.pm or apreq
has stopped parsing it.
- Original Message -
> From: André Warnier
> To: mod_perl list
> Cc:
> Sent: Wed
>From the ASF CMS codebase:
my $subr = $r->lookup_file($file);
my $content_type = $subr->content_type || "";
an undefined content-type will eventually defer to
the default content-type if you've set that in your httpd config.
- Original Message -
> From: André Warnier
1 - 100 of 368 matches
Mail list logo
