Re: [Owasp-input-api-developers] My thoughts on requirements

[Alex R. <al...@se...>]

Gabriel Lawrence wrote:
> Here's some thoughts on high level requirements for the filters project.
> I hope this can serve somewhat as an example, but also as a diving off
> place...
> 

I'm in total agreement with points one and two, but the next one 
concerns me.

> 3. Flexible
> 	This one is somewhat in conflict with the one above, but I think we can
> remedy this in the design process by building mutliple layers that allow
> interaction in different ways. So, while I may want to just have
> something that will slide into to the development platform I'm using, I
> think I'd also like something I can put into a novel application that
> could be built from scratch or something that can be used with an
> application that is using http to do new and exiting things. Along the
> lines of the diff between http proper and http extended to handle
> WebDAV.

So, to clarify this, are we saying that the toolkit itself should be 
flexible (allowing an arbitrarialy complex input syntax, etc) or are we 
specifying that it should be atomic enough to be used in flexible ways? 
I believe that the answer to this question lies a the heart at some of 
our current dissagreement.

So what do you guys think?

-- 
Alex Russell
al...@Se...
al...@ne...