Bill Karwin schrieb:
Because the use cases are so diverse, there may be no single "runner"
solution that solves all of these, and we should not try to make a
single solution.
Agreed.
I suggest that we try to write proposals for solving different use
cases, and treat them as separate components that utilize Zend_Filter
and Zend_Validate. That would be a good way to apply object-oriented
decomposition, and keep Zend_Filter / Zend_Validate classes separate
from the concerns of consumer classes.
I started some notes for a solution similar to the Perl module
HTML::FormValidator, which I used with success on a project some years
ago. I'll write up a brief proposal describing how we might make a
similar solution for Zend Framework.
I don't know that module so I can't say anything about that, but I'm
certainly looking forward to seeing that proposal, and I hope I'll be
able to contribute something to this component :-)
CU
Markus
