Thanks
> My intuitive answer is 'Yes, but fundamentally, you don't
> want to. Tell
> apache your file extension for dynamic images should be handled by
> Embperl, not EmbperlObject'. I believe this is because either the
> difference between Embperl and EmbperlObject is entirely
> devoted to the
> concept of wrapping pages with a standard template, which is exactly
> what you do not want here, or I'm tired and should go to bed
> a few hours
> ago.
I do agree... what I was suggesting is really a bad idea from a design
standpoint. On the other hand, EmbperlObject is more about just
templates when you consider things like the application object, using a
Perl syntax, and so on.
The easiest thing in my situation would have been to do as Andrew
suggested, and create a "images/" sub directory which could override
base.html but still pull in the global inititialization routines in
init.html.
As it sits, my seperate .cgi is working... but I can't handle errors
nicely, other then calling HTML::Embperl::Execute('error.html').
However, when I do that then all the EmbperlObject stuff gets ignored.
See the problem? As soon as you set up another file extension using
standard Embperl, then you can't switch back, other then using the
Location: header to redirect.
Wim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
