Torsten Foertsch wrote:
A few years ago I was in a similar situation. I was working for a big company (~500.000 employees) and someone from the upper management had 'decided' that java was the best tool for all purposes. Then some department had startet a new project and of cource tried to implement it in java using jsp. After 6 weeks of more or less resultless effort the lower management decided to try a competing approach. To my luck the manager had had some positive experience with perl. He hired me and a fellow programmer gave us 2 weeks time to create something to show. After that time the java project was canceled and after another 2 weeks we had created a working system where all the basic requirements were implemented.
As for scalability I am running mod_perl-enhanced apaches on a web server farm consisting of 5 machines making 500.000 visits, 2.000.000 page impressions or 18.000.000 hits a day. Every request on these machines is touched by mod_perl. And the system would run without noticable performance degradation even with only 3 of the machines running.
Torsten, care to reword these bits into a success story, which can be hosted here? http://perl.apache.org/outstanding/success_stories/index.html
See the URL above for the desired format... Thanks.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
