AB> I am not using CGI to handle the information coming in from forms. It's a AB> long story, but believe me, it works out better this way.
URI> i don't believe you. show us proof. 99% of home rolled cgi solutions URI> have bugs and security holes. are you part of the 1% who knows all the URI> little nooks and crannies of the cgi spec? CGI.pm does know them all and URI> handles them all correctly. I am most certainly NOT one who knows all the nooks and crannies. However this is a larger project that I am only picking up my part on. Changing things to use CGI.pm would require a LOT of re-coding. Plus these are things that I should know about. Understanding them better makes me a better coder. I would always rather learn that lean on an already created package. Don't get me wrong of course, I love CGI.PM. Bless them for making it. And I do use it plenty. But I believe this project is going to be done mostly by hand. As for the security, I'm pretty sure that we doing a good job with that. At least good enough for this project..... AB> The advice you guys gave me did indeed fix the problem for mozilla AB> (haven't tested Safari yet) I really just needed teh \n URI> see, with cgi.pm you wouldn't have to worry about multiple browsers as URI> it has been tested with them all. True true. Thanks for your input Uri. --Alex _______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
