[Owasp-input-api-developers] language choice, design doc

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

Hey,

I spoke with Gabe this afternoon and it was agreed that we're going to
use Java as one of the 2 inital development languages. But that leaves
one still undecided. Our thinking is that it'll be much easier for us to
be conscious of cross-language development problems if we force
ourselves to develop for at least 2 very different languages right off
the bat.

That said, I'm hoping the list will have some input as to what our 2nd
language should be. Whatever it is, the development that happens for
that language will be done in a more-or-less procedural way, and so the
language should lend itself to that style of development.

Current thinking is that we might use one of the following:

	* PHP
	* Python
	* Perl
	* C

Other suggestions are of course welcome.


As a final note, expect something vaguely resembling a "design document"
from me by sometime tomorrow afternoon. At the very minimum it will
outline our design philosophy (probably stolen from the vision doc), as
well as technical specifics of how things will be built. Perhaps some
sample usage semantics will be presented. Once I post it, we'll kick it
around a bit before we start coding, but that shouldn't take more than a
couple of days (end of week?).

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