Hi,
Thank you for insights,
I see that scripts written in Perl need a special Perl that supports FastCGI
(see FastCGI Programmer's Guide - Chapter 3, Developing FastCGI Applications
in Perl)
..snip..
"The FastCGI-savvy binaries are extensions of standard Perl, and are intended
to replace your existing Perl installation."..snip..
This is not something I want. I want to use OS's Perl distribution with tools
that work directly with standard distribution.
May be it is time to consider the possibility to convert Perl/Apache/mod_perl
scripts to Erlang Yaws/Mochiweb/WebMachine/Cowboy or even Nitrogen framework.
Another question because I use Erlang on OpenBSD ...
I applied patches from R15B02 to OTP 17.3 and it seems to work as expected
(stress tests, etc). Do you think it is safe this for production environment
as I want to migrate the R14B04 applications to OTP 17.3 ?
It is scheduled for near future to upgrade OTP from R15B02 to 17.3 ?
Bogdan
| Â |
| Â | Â | Â | Â | Â |
| FastCGI Programmer's Guide - Chapter 3, Developing FastCGI Applications in
Perl[Top] [Prev] [Next] [Bottom] 3 Developing FastCGI Applications in Perl
This chapter explains how to code FastCGI applications in Perl. |
| |
| View on www.fastcgi.com | Preview by Yahoo |
| |
| Â |
Â
On Thursday, November 13, 2014 9:36 PM, Stuart Henderson
<s...@spacehopper.org> wrote:
On 2014-11-13, Bogdan Andu <bo...@yahoo.com> wrote:
> Are Perl scripts in FastCGI evaluated in same manner like in mod_perl, or
> everytime a script is invoked by the server the Perl interpreter is invoked
> also ?
If you run them via slowcgi, the interpreter+script will be started from
scratch each time.
To have a persistent Perl process, convert your script to talk FastCGI
directly (see ports/www/fcgi) or via PSGI and a fastcgi adapter, or use
some framework that supports it (in Perl-land you might want to look at
frameworks like Mojolicious, Dancer etc).
> I want to setup a 5.6 machine and test all these cool stuff but for the
moment
> I don't have access to such machine and I would like to see what other
poeple
> experienced with this httpd(8) daemon .
httpd was *very* new in 5.6, you want something newer (-current, or
keep your eye out for patches). If you want to play with fcgi before
updating, nginx and lighttpd support it natively, and apache via a
module - it isn't something new, it has been around for years, it's
pretty much the only standard way to handle cgi-like scripting in a
non-forking webserver. Config methods differ, but scripts should be
portable between all the various http servers.
