On May 8, 2006, at 4:43 PM, Dan Sully wrote:
* Christopher Key shaped the electrons to say...
Can I assume that the position is approximately as follows. It is
agreed
the splitting things up is certainly worthwhile, but that pre Perl
5.8, it
really isn't practical, and requiring Perl 5.8 wasn't acceptable.
Perl 5.8
introduced suitable threading, and the split-scanner is based upon
this.
The intention for version 7 is to move over to apache / mod_perl,
which will
make threading far easier.
Not quite.
1) We're requiring perl 5.8 or higher (preferably 5.8.3) for 6.5
2) split-scanner does not use threading - it simply spawns a
separate process
using Proc::Background (which does the right thing on Windows &
*nix)
3) Those were thoughts for version 7. Nothing is set in stone. At
this point
in time, FastCGI is likley a better alternative than mod_perl,
and that's
still a big "if we decide to use Apache".
There are also pure-Perl solutions that are a lot lighter and easier
to manage, i.e. Net::Server or POE, as Dan mentioned. Or we could
use a light-weight web server such as lighttpd. Apache might be a
bit heavyweight for our needs, which, probably 9 times out of 10, is
just 1 user hitting the web server.
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/beta
