That was a really really specific application. For CGI execution you are better off sticking to something that speaks proper CGI like apache unless you are wanting to have a stand alone perl application (to ship as a web interface for some other POE enabled code or whatever). And even then you are probably better off rewriting your CGI scripts to exist within a POE environment which completely kills the idea of the common gateway interface.
All in all it is going to end up being a lot of work without much gain (if any, comparatively for performance) if you already have a working solution under apache or something. The POE HTTP server solutions are only the bare essentials to manage a TCP connection and filter inbound data to build HTTP::Requests. You will need to write supporting code to get your CGI solutions integrated which may beyond the scope of your project.
-- Nick
Mathieu Longtin wrote:
Hi,
I'm trying to move a bunch of CGI scripts to a POE server, mostly for performance.
Looking at CPAN, I see three different POE component HTTP server:
POE::Component::Server::HTTP POE::Component::Server::SimpleHTTP POE::Component::Server::HTTPServer
All of which have been patched in the last six months.
So, I guess my questions are: - What are the differences, beside the names? - Which should I use?
Thanks
-Mathieu
_______________________________
Do you Yahoo!?
Express yourself with Y! Messenger! Free. Download now. http://messenger.yahoo.com
