Stupid story time This probably isn't novel to anyone else, but it was a huge deal to me at the time.
One morning my manager came and told me that sales had sold a "splash" ad (meaning a big annoying ad was supposed to come up on a users first request to the site, no matter where on the site the request is for.) Anyway, we'd never even talked about doing anything like that, and suddenly we had a client expecting it to go up in a week. At first i had no idea how we were going to do it, because of the mix of static and dynamic content on the site. I ended up doing the whole thing in a couple of hours as an AccessHandler. adam -----Original Message----- From: Frank Wiles [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 30, 2004 11:26 AM To: Dan Brian Cc: [EMAIL PROTECTED] Subject: Re: mod_perl marketing On Tue, 30 Nov 2004 09:10:32 -0700 Dan Brian <[EMAIL PROTECTED]> wrote: > I would suggest that future mp2 articles (on perl.com and elsewhere) > take some time to explain the Apache API and why it is by far the best > choice for Perl server development, before diving into the particulars > of accomplishing something with it. I've got an article coming out in SysAdmin Magazine in January that is more about the power of the Apache API than about the normal response phase workings. I think the API is what really separates mod_perl from other similar technologies. And I think we all agree that this is what needs to be stressed more to the public to gain better adoption. --------------------------------- Frank Wiles <[EMAIL PROTECTED]> http://www.wiles.org --------------------------------- -- 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 -- 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
