On Fri, 2006-03-31 at 09:36 -0700, David Romero wrote: > You can write large aplications on separated handlers but is so slow > write every new module on httpd.conf
Is it? I find that most large applications break down into less than a dozen different handlers. It seems quite easy to put these in httpd.conf to me. If it bothers you, there are many alternatives, like Apache::Dispatch, or web frameworks like the ones here: http://perl.apache.org/products/app-server.html (Didn't we add Catalyst and Maypole to this page already? I thought I remembered that.) > and on this way can't share db > conections Yes you can. Apache::DBI and DBI->connect_cached work fine across different modules. > and consume large amount of ram on load common functions on > every module. If you put those functions into a module and use that module from multiple handlers, it will only get loaded once in each perl interpreter. It will not use more memory. > Other way is write one handler and load modules dinamicaly for content, > but you need to send a common var to every module and mayve this use > large amount of memory. I'm not sure what you mean by this. What's the "common var" that you're talking about? - Perrin
