Anyone out there willing to try some rough benchmarks on
tcpperl vs. tcpserver+pperl vs. tcpserver+speedycgi vs. tcpserver+straight_perl?
-jc
At 12:43 PM 3/12/2004, Charlie Brady wrote:
On Wed, 10 Mar 2004, Charlie Brady wrote:
> http://cr.yp.to/ucspi-tcp/tcpserver.html > > The "traditional" qpsmtpd run script teams tcpserver and perl OK.
Here's another possible solution:
http://www.superscript.com/ucspi-tcphandle/tcpperl.html
It seems to be more or less tcpserver with an embedded perl interpretor.
tcpperl forks the requested number of children, each listening for TCP client connections. Before handling any requests, each child parses and runs the perl code in file. The file should end with a true expression, like a module.
To handle a request, a child process executes prog as a perl subroutine, with file descriptor 0 reading from the network and file descriptor 1 writing to the network. Before handling the request, the child sets certain environment variables, a la tcpserver.
--- Charlie
