Re: RFC: Implementing a core anti-XSS escaping class
| From: | Michael Stowe | Date: | Wed, 19 Sep 2012 16:21:39 +0000 |
| Subject: | Re: RFC: Implementing a core anti-XSS escaping class | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-63149@lists.php.net to get a copy of this message | ||
*"Oh goodness no, let's please only do OOP with the language features.
Creating ridiculous "procedural" OOP abstractions helps absolutely nobody"*
Andrew, I'm the biggest advocate of OOP out there, but the purpose of this
is to provide a nice convenient layer for all developers to use to properly
escape code and increase security within their applications. As such, we
need to cater to the resistance...err, I mean Procedural Purists and those
who are beginning PHP development and are not yet comfortable with OOP.
- Mike
On Wed, Sep 19, 2012 at 11:17 AM, Andrew Faulds <ajf@ajf.me> wrote:
> On 19/09/12 17:16, Lars Strojny wrote:
>
>> Hi,
>>
>>
>> There seems to be a need for a procedural API. As their is one, let’s do
>> it similar to how MySQLi etc. does it and use a context resource:
>>
>> $ctx = escape_context_create('UTF-8')**;
>> $str = escape_html_attr($ctx, $str);
>>
>> And so on.
>>
>> cu,
>> Lars
>>
> Oh goodness no, let's please only do OOP with the language features.
> Creating ridiculous "procedural" OOP abstractions helps absolutely nobody..
>
>
> --
> Andrew Faulds
> http://ajf.me/
>
>
--
-----------------------
"My command is this: Love each other as I
have loved you." John 15:12
-----------------------