Tomas Doran wrote:
If you try to run multiple copies of the same application in the same
perl process, it won't work like you expect - the setting will come
from the first application loaded..
Your solution just makes it much easier to have multiple deployment
environments with different configurations, but these environments
still have to have a different perl interpreter each.
True, we did need to keep each application using processes which are
separate. This was an issue when we used PerlEx (the ActivePerl style
mod_perl approach) but we now use FastCGI (clients use Windows, etc.)
and IIS freely creates many processes, and makes it really easy to set
environment variables for them from its configuration files. The IIS
FastCGI mechanism was developed closely with Zend, and I guess PHP faced
the same kind of issue, and this was their solution.
I'll wikify the config trick for now; we're close to production
deadlines right now, but I do want to get this out there!
--S
--
Stuart Watt
ARM Product Developer
Information Balance
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
