[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

refactoring client's decision


I've taken over some code for a client. They've built a framework that used to run under mod_perl and changed it later, because of problems they had - what problems remains unknown - to cgi. Ofcourse I'm curious why they changed it. Here's my view: they create a parent App::Handler and in every virtual host they create a Site::Handler which has App::Handler as base. My first guess is that under mod_perl you don't know which Site::Handler will be called. Ofcourse, at first, the handler you're actually pointing to will be called, but if you change the request to another virtualhost, the wrong handler will be called.

This would explain why it's running perfectly under cgi, because in every script call the correct lib path is defined.

So, my first question is: am I right?
Secondly, what if we're running the cgi under speedycgi?

Thx,
Marc


Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.