Re: Concerns about Zend_Filter_Input

Why the push to 1.0 so fast, when things can't as readily be changed after?

With so many changes in 0.8 and now some serious 0.9 changes, might make
sense to slow down the run-up to 1.0 a bit. If not, then the same level of
change will occur post 1.0 and instead of point releases, there'll be a
bi-monthly majorversion jump.

I'd propose a 0.8.5, 0.9.5 and 0.9.9 before 1.0 might give time to get all
the API changes out of the way.

$0.02

Kevin
----- Original Message -----
From: "Bill Karwin" <bill.k@...>
To: "Ed Finkler" <coj@...>
Cc: "Zend FW Core List" <fw-core@...>
Sent: Tuesday, March 13, 2007 12:58 PM
Subject: RE: [fw-core] Concerns about Zend_Filter_Input


> -----Original Message-----
> From: Ed Finkler [mailto:coj@...]
>
> 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?"

No, there will not be such a component in ZF 1.0.

We're very close to our scheduled feature-freeze for Zend Framework 1.0
(March 15).  A solution to satisfy the use case you describe is not
going to be implemented by our deadline.

> 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.

Right, currently the Zend_Filter classes operate on scalars.  Using
these classes to apply filtering and validation to arrays or other
aggregations of data is left for the developer to do, in a manner
appropriate for his application.

We encourage proposals for solutions that utilize the Zend_Filter and
Zend_Validate classes, to apply filtering and validation to aggregations
of input data.  So far there has been discussion, but no design has been
formally proposed.

We will evaluate the proposals and a solution will be added in a future
release of Zend Framework (e.g. 1.1 or later).

Regards,
Bill Karwin