Re: [Owasp-input-api-developers] Design Doc

[Mark C. <ma...@cu...>]

Cool, just making sure things didn't stray like they 
did again ;-)

---- Gabriel Lawrence <ga...@bu...> 
wrote:
> On Tue, 2002-09-24 at 00:14, Mark Curphey wrote:
> > Cheers.
> > 
> > On Tue, 2002-09-24 at 06:27, 
Chr...@ey... wrote:
> > > Mark,
> > > 
> > > I think a version of the Filters API 
implemented as a Servlet 2.3 Filter 
> > > could be useful, and I have proposed such an 
implementation on this list 
> > > in the past.  It is something I will work on, 
but it may not be consistent 
> > > with the approach we'll take at the outset, 
which is to create filters to 
> > > be used at boundaries.
> > 
> > Just my 2 cents worth but I would suggest you 
chat the the PM (Gabe) and
> > tech lead (Alex) to ensure its in unison with 
whats been mutually agreed
> > on, to ensure inclusion with the project release 
files.
> 
> The idea that Alex and I had discussed in the past 
was that of a layered
> approach. That being that the first bit of work we 
do was more nuts and
> bolts, and then this could be used to make a more 
plug and play solution
> a la servlet filters... So its not out of sync 
necessarily with what we
> want to do, but what we are really after is making 
first tools and then
> solutions...
> 
> -gabe
> 
> 
> -- 
> Gabriel Lawrence
> CTO
> Butterfly Security <www.butterflysecurity.com>
> (408) 333-9948
> ga...@bu...
> 
> 
> 
> ---------------------------------------------------
----
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Owasp-input-api-developers mailing list
> Owa...@li...
> https://lists.sourceforge.net/lists/listinfo/owasp-
input-api-developers
> 
>