Re: Filters Extension
Jonathan Swartz <[email protected]> Fri, 11 Jun 2010 15:57:55 -0700
| Newsgroups | gmane.comp.web.mason.devel |
|---|---|
| Message-ID | <[email protected]> |
That looks nice Daniel! Is this written in a way that it can be used as an extension, or would it have to be added to the core? Jon On May 31, 2010, at 5:30 AM, Daniel Zulla wrote: > Hi, > > i want sugget an input filter, based on MooseX::Types, cause i just > think > if the variables given to your application > don't match your needs, you shouldn't continue the execution. that > improves > security and performance. example given: > if you expect an integer<5-100> as $foo, but you get a string, you > don't > have to go on, and execute the sql statement, > cause you already know, it will fail. > > i wrote am example extension for the lexer [1] and the compiler [2], > and a > in-use example [3]. > > if the parameters don't match, or if the request method is wrong, a > default > error template, showing the specified error messages, > should be delivered - unless no <%callback> is set. > > line 60-61 in compiler.txt is calling is_Int from Moose, checking if > the > paremeter is an integer. > > what do you guys think about it? > > greets, > scio > > [1] Lexer Code: http://scix.de/lexical.txt > [2] Compiler Code: http://scix.de/compiler.txt > [3] In-Use Example: http://scix.de/in_use.txt > > ------------------------------------------------------------------------------ > > _______________________________________________ > Mason-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mason-devel ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo