On 9/8/05, Kieren Diment <[EMAIL PROTECTED]> wrote: > > > Cool. THanks. I'm a little confused about something in the Static > > pages section , p. 24 of the PDF. He says "We don't want static pages > > like the CSS processed through the whole Maypole system . . . " What > > exactly does he mean about CSS being processed through Maypole? My > > css is strictly in the HTML or so i think. > > > > I think that he means that if you're path to your app is /path/to/app > and you have content that's served in the normal (apache httpd > no-mod-perl) way at /path/to/app/static, (so going to > http://your.site/path/to/ap/static/doc.html serves up the doc without > going through the stuff in Maypole::Manual::Request) , you can bypass > the creation of a $r object by ignoring it in Maypole through the way > he suggests. >
Thanks Kieren. I think you are right. And that is a good tip. What I still do not understand is why he used "CSS" as and example of a static page.. Maybe it was just an editing error. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Maypole-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/maypole-users
