Bill Karwin wrote:
> Hi Ed,
>
>
>
> Actually, the implementations of Zend_Filter and Zend_Filter_Input in
> earlier preview releases of Zend Framework have been _/replaced/_ by a
> much better object-oriented class design that provides similar
> functionality. It’s better because it also serves as an extensible
> framework for developers to implement custom filters and validators.
> And also, an application needs to load only the filters and validators
> that it needs, instead of a monolithic class that contains all filters
> and validators.
I can see that creating my own filters is significantly easier, and
that's a win, no doubt.
> There is still more work to do, to make the process of filtering and
> validation even easier to use. We’ll enhance the solution in future
> versions of Zend Framework after 1.0. For example, we intend to design
> an easy-to-use component to apply filtering/validation logic against
> aggregations of web input data.
Let me reiterate my second question:
"2) Will a similar replacement component, one that forces developers to
access user input via a filtering API, be included in the 1.0RC?"
I've certainly been known to miss things staring me in the face before,
but I don't see anything in the new Zend_Filter that would allow me to
do bootstrap filtering like I could with Zend_Input_Filter:
<code>
$f_POST = new Zend_Filter_Input($_POST);
$f_GET = new Zend_Filter_Input($_GET);
$f_COOKIE = new Zend_Filter_Input($_COOKIE);
$f_SERVER = new Zend_Filter_Input($_SERVER);
</code>
Can any of the filter classes that are now part of the ZFW process
arrays? All of the usage cases I see are handling scalars.
Again, I want to make sure I'm not missing something before forming an
opinion.
--
Ed Finkler
Web and Security Archive Administrator
CERIAS - Purdue University
http://www.cerias.purdue.edu/v: 765.496.6762 f: 765.496.3181