> like try to write your own CGI parser. Libraries like cgic at
> http://www.boutell.com/cgic/ and cgicc at http://www.cgicc.org make a
> lot
> more sense than reinventing that particular wheel yourself. They
> also
> address the buffer overflow problem directly by using strings, or
> forcing
> the author to state how much data they are capable of receiving.
>
> Now that I have my infrastructure libraries, C/C++ and PHP are about
> equivalent in speed for me to develop an app, and if complexity is
> involved C++ will be the best bet.
I used cgicc.
It's good workable code, but it's a pain sometimes to understand!
__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/
