Re^4: HTTP::Server::Simple forking/SSL/IPv6

[cavac]

in reply to Re^3: HTTP::Server::Simple forking/SSL/IPv6
in thread HTTP::Server::Simple forking/SSL/IPv6

Well, in my case there's probably a bit more work involved. I also do things like on-the-fly HTTP compression, keeping database connections open, etc...

If i understand correctly, the various files are loaded on request and not on startup? Or am i misreading the documentation?

If everything is in an anonymous subroutine, how does debugging work? With Maplat (my framework), i just start the script with the appropriate breakpoints set and then surf to the page i want to debug.

Edit: On a personal note, Corion, i really love the Power-to-Ethernet cable on your homenode. Where can i get one?

[Corion]

Depending on the backend (HTTP::Server::Simple, Starman, Corona, ...) you get persistence of connections and other values, or not (for example with Plack::Handler::CGI). The files are loaded on program startup, which is server startup for the permanent servers and page request for CGI.

Having in-process debugging is something I have no experience with. Only the outermost part of your web application is an anonymous subroutine, everything else can be named subroutines, so finding your way around should work the same still. I guess a quick test whether your debugging setup works would be to just use one of the Plack example applications, set your breakpoints and see whether the program is debuggable under whatever server you plan to use.