I've been playing with Embperl v2 lately. I am very impressed with the
ability to have various Syntaxes, and to be able to easily switch
amongst them at will, even withing the same Embperl object.
Has anybody tried running their current mod_include websites under
Embperl 2? The only thing that's been hooping me up so far in the
inability to do these two types of includes:
<!--#include virtual="/some/file.html">
<!--#exec cgi="/cgi-bin/list-stuff.cgi">
I realize that doing the #exec cgi is bad, as it causes another perl
interpeter to be forked, even when running under mod_perl. My goal is to
replace all these #exec CGI calls with similiar calls to Embperl
objects. If this can be done using the Embperl SSI syntax calls, that
means we don't have go through and change all the 3-400 files (mostly
static HTML, but some Apache::Registry scripts and mod_perl handlers as
well)... all we need to do is change the header SSI (/header.ssi) to do
this instead:
<!--#include embperl="/list-stuff.epl">
Our web designer / content people are really rejecting the idea of
having to learn EmbperlObject, even though it will save him a lot of
time and code in the long run. Being able to use
HTML::Embperl::Syntax::SSI for all his stuff means we get a faster site,
the perl coders can use EmbperlObject and just Execute('/header.ssi')
and footer.ssi, and be done.
Other then the above questions/comments, does anybody else have stories
to share (or links or whatever) of SSI->Embperl migrations? Or SSI to
something else?
--
Regards,
Wim Kerkhoff, Software Engineer
Merilus, Inc. -|- http://www.merilus.com
Email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
