DarkAge
asked on
ASP vs. CGI/Perl
Can ASP replace CGI/Perl functionality? Totaly?
As MasseyM says, you could substitute ASP for Perl/CGI. But why would you want to?
The real problem is that ASP is a proprietary development method that's pretty much limited to microsoft's web server.The O'Reilly web server has an ASP implementation and there are a few weak attempts at Unix ports, but mostly ASP is Windows/IIS only.
Compare ASP to established, open development methods like CGI and Perl. Perl is widely used... in fact it's probably the MOST widely used web development language of all. Easy to learn, but with the power of C++ for those who need it. CGI apps (and WIN-CGI) can be designed to run nearly unchanged regardless of what web server software and operating system they are running on. ASP can't do that.
Even with the benefits of being open, free and cross-platform, I personally like Perl and CGI because of the vast libraries of tools, documentation and modules already written. There are far more collections of Perl and CGI scripts available than ASP scripts... I dunno about you, but I'd rather use someone else's code than write from scratch... THAT is where perl and CGI really outshines ASP for me. Most of the web apps I need to develop can be built in perl using a modules from CPAN and a few lines of custom code. If you add an embedded Perl method to your web server (wuch as ePerl or embperl) you can stick perl code directly in your html documents without having to write separate CGI scripts.
The real problem is that ASP is a proprietary development method that's pretty much limited to microsoft's web server.The O'Reilly web server has an ASP implementation and there are a few weak attempts at Unix ports, but mostly ASP is Windows/IIS only.
Compare ASP to established, open development methods like CGI and Perl. Perl is widely used... in fact it's probably the MOST widely used web development language of all. Easy to learn, but with the power of C++ for those who need it. CGI apps (and WIN-CGI) can be designed to run nearly unchanged regardless of what web server software and operating system they are running on. ASP can't do that.
Even with the benefits of being open, free and cross-platform, I personally like Perl and CGI because of the vast libraries of tools, documentation and modules already written. There are far more collections of Perl and CGI scripts available than ASP scripts... I dunno about you, but I'd rather use someone else's code than write from scratch... THAT is where perl and CGI really outshines ASP for me. Most of the web apps I need to develop can be built in perl using a modules from CPAN and a few lines of custom code. If you add an embedded Perl method to your web server (wuch as ePerl or embperl) you can stick perl code directly in your html documents without having to write separate CGI scripts.
ASKER
Okay Okay, Wait...
I working in IIS enviroment and dont give for other WEB servers.
In that case dose ASP is the best choice?
I working in IIS enviroment and dont give for other WEB servers.
In that case dose ASP is the best choice?
As my answer above states. YES. It is designed specifically for IIS and works just as well if not better on the NT servers.
.asp when implemented properly, *and* extended works well.
Perl however IS the best thing to use (unless you hook up
C to your webengine). You can get Activestate Perl for IIS
and that gives you everything you need.
Perl however IS the best thing to use (unless you hook up
C to your webengine). You can get Activestate Perl for IIS
and that gives you everything you need.
ASKER
Okay, I had my answers, How to I grade the answer and give you the points?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
BUT, I don't think it will. People are to familiar and like CGI/PERL.