darren chamberlain wrote: > > Since you are using mod_perl, you can take advantage of Apache's > subrequest architecture and a plugin:
<example snipped> > This is completely untested, of course. I'll test this out as soon as I > get a chance and report on the results... > (*smacking myself*) For whatever reason, this didn't cross my mind or maybe I did and I was so buried in post-it notes about tie'ing STDOUT I just got "more dummer." The problem I kept running into was I was calling run() on the subreq and thus having the output spewed back at me at very inoppertune times. In your example, you did an end run around the problem and I am dreadfully ashamed I didn't think of it myself. :) Just as a general gripe (I know this is a bad idea but I'm going to do it anyway in hopes that I'm not alone) it would be nice if mod_perl help subrequest output and all print'd content the same way it does with headers as it would be easier (sometimes) to do things slightly out of normal order. Ok, now that I've pegged myself as a lamer... :) > Ah. My method still uses subrequests, but I think it's a little > cleaner than retying. > That is most certainly is! > Out of curiosity, though, why aren't you just using INCLUDE directly, > with an INCLUDE_PATH that includes your /components URI (using > File::Spec->catfile($r->document_root, "components") or similar)? > The reason why is because /components/* is a virtual apache location, not a real directory with real files. Everything under /components/ for this site is mod_perl handlers like /components/login, /components/navigation, etc, etc. Just after the time of my email, I did manage to find someone in the #perl channel on OPN that suggested (in short) just using TT's plugin arch as you have. This person (who was extremely helpful) felt that the concerns I had regarding the separation of display code vs. submit handler code (be it logical or physical) wasn't something that would be overcome by actually achieving my ideal scenario. I think I'm going to give it a serious go with Template::Plugin and see what happens. Once again, thanks, and I apologize if I've made the list experience deja-vu because my brain is leaking this week. -- eric sammer <[EMAIL PROTECTED]> LinuxSTEP <http://www.linuxstep.org> InterfaceWM <http://interfacewm.sourceforge.net>
