On Wed, Dec 3, 2008 at 1:26 PM, Arthus Erea <[EMAIL PROTECTED]> wrote:
> > I do think both sides are making some good points, and we both have > the common goal: make unfiltered data hard to get, and filtered data > easy. > > In the proposed implementation (with Input::*), we should *definitely* > clear the superglobals, so people are forced to go through more hoops > to get unfiltered data. I think it's worth pointing out again that this exact pattern is used in two popular frameworks (and I'm sure several more). That makes it more familiar to people already and obviously can't be *that* bad or it wouldn't have lasted this long. I think making it clear that filtering is the default (by providing a default value of true) is enough. If I need to get to raw data (and it doesn't matter why, we can't possibly anticipate all use cases), I should damned well be able to without jumping through hoops. It would piss me off to have to constantly jump through hoops and change the way I code just to get a raw, unfiltered, value, and I know it would piss each one of you off if you came into a framework or app where you had to and had to write code. Again, make the default clearly be filtered data and educate naive developers - don't throw the baby out with the bathwater and punish those developers that know what they're doing already. > > > Could we potentially sink a plugin hook within Input::*($index, > false), such that a plugin could be activated which would provide > logging information of all instances. > > I am not set on the false syntax – I think it should be even harder to > get the raw values. Maybe having to go through the straight array > instead. At worst (read: easiest), we could stick in an EventLog every time someone calls one with 'false' as the filter argument. When in doubt, log the hell out of it. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
