Re: PHPFrom: Nathan Cook (firstname.lastname@example.org)
- Previous message: Antonomasia: "Re: appropriate security restrictions for untrusted client-side code?"
- In reply to: email@example.com: "Re: PHP"
- Next in thread: David Wheeler: "Re: PHP"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Message-ID: <firstname.lastname@example.org> From: "Nathan Cook" <email@example.com> To: <firstname.lastname@example.org> Subject: Re: PHP Date: Wed, 22 Aug 2001 14:55:51 -0600
> One can use a MVC model, and have only one entry in the site to do the
> `dispatching'. That entry can do proper checkings and all.
It seems to me like it would be extremely simple to create an auto prepend
script (http://www.zend.com/zend/spotlight/prepend.php#Heading3) and just have
that run before every page is processed to set the variables or unset the
variables that are suspect. That way no matter what page they entered on, you
could regulate it.