After the third action controller in a row I have refactored to use REQUEST instead of GET/POST directly and I'm sitting here thinking...
I could really clean up the code in each controller if I used an intercepting filter in the front controller and had the intercepting filter somehow set the REQUEST object up with filtered data. That way I just have to access the REQUEST object in the controllers and not have to worry about filtering data...
Basically I could implement this as a simple regex lookup mapped to the given name of the variables. Ideally I could associate the regex based on type and avoid the duplication occuring when filtering first name and last name (strings). However I could possibly have each filter cross reference existing filters if they accomplish the same end result...
What do you think? What do you do? Do you filter inside each individual controller or would it make more sense to filter using an "Intercepting Filter" - hence I figure that is where the name came from.
Cheers