Hello all,

I'm very pleased to announce Yet Another HTTP server component:

http://search.cpan.org/perldoc?POEx::HTTP::Server

POEx::HTTP::Server is a clean POE implementation of an HTTP server.  It uses
POEx::URI to simplify event specification.  It allows limiting connection
concurrency and implements HTTP 1.1 keep-alive.  It has built in
compatibility with POE::Component::Daemon's prefork server support.

POEx::HTTP::Server also includes a method for easily sending a static file
to the browser, with HEAD and If-Modified-Since support.  Sys::Sendfile is
used for the transfer when available.

POEx::HTTP::Server enforces some of the HTTP 1.1 requirements, such as
the Content-Length and Date headers.

To answer the obvious questions:

POEx::HTTP::Server differs from POE::Component::Server::HTTP by having a
cleaner code base and by being actively maintained.  

POEx::HTTP::Server differs from POE::Component::Server::SimpleHTTP by not
using Moose and not using the YELLING-STYLE of parameter passing.

http://search.cpan.org/perldoc?POEx::HTTP::Server

-Philip

Reply via email to