Seems like I remember Chris saying that losing the mod_perl dependence was something relatively high on his TODO list. While I haven't looked at the code lately, it might be something easy to do. I remember one application that "required" mod_perl because it used $r->print() and Apache::Request methods that have CGI counterparts. I think I spent 10 minutes changing it to run under CGI.
At a minimum you should probably look at the frameworks Perrin mentioned because they have a lot of very useful functionality you might be able to implement for your framework. | [reply] |
I think the reason OpenInteract needs mod_perl has more to do with performance than with specific module dependencies. The life-cycle of mod_perl applications allows you to use a larger codebase without the speed penalty of compiling it on each request, and cache expensive resources like database handles. I know that people have made, for example, Mason run under CGI, but it was too slow to be useful that way.
| [reply] |
| [reply] |
| [reply] |