If one were building a system from scratch, I'd certainly agree with you. When
one puts embperl into an already-built environment using an extension (.html)
that is already in wide use, you find that you often wish to disable embperl
on file that already exist and do not use embperl. Our choice was not made
lightly. It was the best solution to a murky situation. If you care, I could
go into detail on it.
Since there's no UnSetHandler, once you've set the handler for a certain file
pattern ( .*\.html$ ), you're stuck with it across the entirety of the site.
Regards,
Christian
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On
> Behalf Of indrek siitan
> Sent: Thursday, March 23, 2000 10:13 AM
> To: Christian Gilmore; [EMAIL PROTECTED]
> Subject: RE: Two feature requests
>
>
> Hi,
>
> > In our use of embperl on the www.research.att.com web site,
> > we've come across a number of pains with respect to embperl
> > and people who have pages that don't want embperl.
>
> shouldn't the system work the other way around - enable embperl
> where you need it (from .htaccess file for example), not disable
> where you don't?
>
>
> Rgds,
> Tfr
>
> --==< [EMAIL PROTECTED] >==< http://tfr.cafe.ee/ >==<
> +1-504-4467425 >==--
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
