>
> Before I get too far into this, is it a reasonable solution to use the
> EMBPERL_INPUT_FUNC feature for combining SSI and Embperl code in the
> same page?
>
> I probably want to migrate away from SSI and do everything within the
> Embperl framework, but for initiating the site and using my current SSI
> templates, headers, trailers, etc., I want to begin using Embperl right
> away along with SSI. I am not satisfied (yet) with the EmbperlFilter
> solution of chaining the handlers, for various reasons.
>
> I came across the ProxyInput() function and followed the hint regarding
> using this for SSI. My setup works fine on the few test pages I've
> cobbled together. I just would like to hear from anyone who might have
> thoughts on this technique, either positive or negative.
>
EMBPERL_INPUT_FUNC was initial implemented exactly for that reason. To post
process mod_include (not Apache::SSI, this works better with Apache::Filter)
pages with Embperl. This should work, but Embperl can't cache the compiled
Perl code of such a page, unless it has a modification time header (which a
normal SSI page won't have). Also I had trouble using this under NT, but
this was about two years ago, so this might have changed.
Gerald
BTW. Make sure you have the newest version of Embperl (1.2.1), because there
was recently some fixes in the EMBPERL_INPUT_FUNC code.
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925151
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
