i've heard already about Dancer, but all examples were self-contained, i.e Dancer started its own webserver and my goal was to take advantage of Apache's VirtualHosts in order to not tinker too much about threading, forking, handling whole protocol layer "by hand" and so on.
Also, using webserver's name-based virtualhosts makes my "application" easliy scalable: for development purposes i can have it running on single machine, running single instance of apache on single 80 port, and separate front from back only when usage scenario will require it.
However, i must admit that didn't took too much time to check Dancer's capabiliites.
But if you said that it's wort to give a try, i at least check if Dancer's app can be embedded into Apache's CGI/PSGI
| [reply] [Watch: Dir/Any] |
Dancer2::Manual::Deployment shows how you can run Dancer2 apps via CGI, FastCGI, or PSGI. CGI, I really wouldn't recommend because it will perform horribly, but the other options should work fine. Another possibility it to run it standalone and use Apache mod_proxy to act as a frontend for it.
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |