Yes, that's what my module does.

"Integrates nicely" is not a 100% true, though. While it easy enough to use Net::Server with HSS, there are some pitfalls, though. Like, you have to disable the two calls to "binmode" in the _process_request() sub when (and only when) using SSL.

So, HSSCP is not "revolutionary", "ultimate" or "the best"; rather i took all the workarounds and steps-to-make-it-work i had come up with and put them into a more or less easy-to-use module. With the hope that this module now makes it easier for beginners to set up a preforking all-perl webserver.

For more complex tasks, there are a lot of frameworks around like Catalyst or the ("cavac has still not released 1.0 and working examples") Maplat server.

Um. I'm not sure it's such a great idea after all. I mean, HSS is awesome for prototyping but after several months of extensive testing I'm much less inclined to put it in production, preforking or not. Anyway, it's easy enough to setup reverse proxy scenario with a bona fide HTTP server even for prototyping, so what's the reason for adding SSL and stuff?

Besides, Plack is the way to go these days. It's not an ideal solution but it's near enough so the only reason for avoiding it I see is compatibility to Perl versions older than 5.8. YMMV though.

Regards,
Alex.