I know that not all of the monks who have responded were in "Backlash Mode", we just want to set you (and all perl seekers) on the right path. CGI is the right path for doing cgi work.
If you have read the nodes given, and you still think CGI is not the right path (for you or others you know), please tell us why. But you will need to back up what you say, as many of the monks here have spent years cleaning up messy and insecure web apps.
Perl programming and scheduling in the corporate world,
as explained by dragonchild:
"Uhh ... that'll take me three weeks, broken down as follows: 1 day for coding, the rest for meetings to explain why I only need 1 day for coding."
| [reply] |
As penance, Brother outcast (and probably to get the XP back {g} ), I suggest you write an node that points out *at least* 5 things wrong with this bit of code - I saw that at first glance, and I reckon others would see a lot more :) Then shalt thou truly be forgiven...
Cheers
Ben. | [reply] |
I do not think that any of us were trying to be mean or nasty. We simply want the world to know that rolling your own CGI parser can introduce serious security holes. | [reply] |