[Esapi-user] Regarding ESAPI WAF

Jim Manico jim.manico at owasp.org
Tue Nov 16 06:20:00 EST 2010

+1 remove

-Jim Manico

On Nov 15, 2010, at 6:50 PM, "Kevin W. Wall" <kevin.w.wall at gmail.com> wrote:

> On 11/15/2010 11:34 PM, Chris Schmidt wrote:
>> I am forwarding this message along for Arshan
>> ---
>> Devs and users,
>> For the final 2.0 release we wanted to more tightly integrate the WAF into
>> the rest of ESAPI. This means that the WAF will use the ESAPI logger instead
>> of log4j, its exceptions will extend ESAPI exceptions, etc. Does anyone
>> object to these old API being removed instead of deprecated? The reason we'd
>> like to remove entirely as opposed to deprecate is to remove dependencies on
>> things like log4j which would otherwise hang around only to satisfy the
>> deprecated methods.
>> Looking for your vote on this - remove or deprecate?
>> Arshan
> +1 for burning it to the ground (i.e., removal)
> -- 
> Kevin W. Wall
> "The most likely way for the world to be destroyed, most experts agree,
> is by accident. That's where we come in; we're computer professionals.
> We cause accidents."        -- Nathaniel Borenstein, co-creator of MIME
> _______________________________________________
> Esapi-user mailing list
> Esapi-user at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/esapi-user

More information about the Esapi-user mailing list