|
> bypass the selection page. All he had to change was the > form - the > CGI app was robust enough to handle the different HTTP > request > without change. (I don't know what language he was > using, probably > Perl.) > Hans, it wouldn't take much at all to make a CGIParse wrapper that wouldn't "care" if it was GET or POST. As a matter of fact, the CGIDEV2 kit does this. And, it also allows you to retrieve mutliple values for the same field, and it doesn't need to use the CGIParse API to do this, which was brilliant in my opinion. Before we could use CGIParse, there wasn't an easy way to do this. But, CGIDEV2 had the capability. The tools you're used to using happen to have system/other developers that add all these cool things. We must do it ourselves because there is not as much exposure/support. Doesn't make one better than the other, but, it does mean anything that is done with one CGI language can be done with any of them, pretty much.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
