I disagree on that point. In my opinion, Input::post($index) *is* easier than $_POST, especially for someone who is used to the Habari way. While outside developers might mess around with globals and such, Habari developers are used to the ***::*** format for getting something.
Furthermore, the syntax does _exactly_ what we intend. It makes filtered the default, but makes unfiltered values possible. Overall, it just seems like a much cleaner approach. On Dec 2, 2008, at 5:55 PM, Owen Winkler wrote: > The reason we've avoided this approach is to implement security in a > good way, abiding by the rule "Make it easier to do the right thing by > default". The Input::foo() functions in other frameworks don't make > it > easier to do the right thing. > > Although the idea may seem more concrete, it's just a different way of > doing input filtering that people would need to learn and (more > importantly) also apply correctly. It's probably a greater learning > curve than switching from count($_POST) to $_POST->count(), simply > because until you try to do something silly like count the number of > post submissions, you'd never encounter the problem. > > On the other hand, you'd likely be using input values all the time and > would need to evaluate, as most devs simply don't know how to do, > whether a value should be filtered or not. Using the SuperGlobal > class > as-is makes the default choice easy for those who don't look any > deeper, > and yet provides the required additional power to those who do. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
