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

[Nik C. <ni...@ni...>]

On Tue, 27 Aug 2002, Christopher Todd wrote:

> > 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.
>
> +1
>
> > 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.
>
> Makes sense to me, so long as everyone goes into this understanding that one
> of our goals is to be flexible and try to work out these issues.  I think
> our discussion about the testing tool/framework is a good example of how we
> all have different biases, *which is a Good Thing*, but to succeed, we all
> need to understand that the Perl folks have it right in that "There is more
> than one way to do it."  :-)
>
> > Current thinking is that we might use one of the following:
> >
> > 	* PHP
> > 	* Python
> > 	* Perl
> > 	* C
>
> I would argue for Perl.  It's popular, very different from Java, and we have
> Perl developers on this list.

I would have to vote for PHP, since I am not confident enough with Perl or
Java to write anything very serious, and do not understand the full scope
of either language. I am currently doing a lot of PHP work and could
easily justify developing PHP filters during work time, and could start on
it ASAP.

Filters for C are going to be very different to the other languages, since
it is a lower level language with its own issues. For full filter
functionality in C you will probably find yourself re-writting (or
writting wrappers for) a lot of the existing libc functions. How popular
is C in web apps nowadays anyway?

Is there going to be a requirments document for the testing tool and
framework written also? I assume the tool will be written in perl.

-Nik