On Fri, 2004-02-13 at 10:26, Ged Haywood wrote: [snip] > > Since I'm building the code from scratch, I am currently using > > Apache::Registry > > If I were you I wouldn't do that either. > > > My initial (newb) impression was that PerlRun is for quick porting, > > Registry is more proper. > > Nope. Both are horrible hacks.
So what is a good alternative to Apache::Registry? My impression was that this is the thing to use unless you want the extra functionality of something like HTML::Mason. I read: http://perl.apache.org/docs/1.0/guide/performance.html#Apache__Registry_PerlHandler_vs__Custom_PerlHandler which shows Apache::Registry is slightly slower (but not by much) than writing a custom Handler. In my case I have 100's of scripts I'd have to write custom handlers for which seems like a maintenance nightmare. If I wrote a generalized handler, I'd just be reinventing Apache::Registry. Has someone reinvented Apache::Registry in a way that isn't a horrible hack? -- |- Garth Webb -| |- [EMAIL PROTECTED] -|
signature.asc
Description: This is a digitally signed message part
