in reply to cgi and asp

CGI is easy to suid (i.e. run as the user who owns the script - which provides better security on shared systems), but launches a new instance of the Perl interpretor for every request.

ASP keeps the PerlScript interpretor in memory so is faster, but tends towards the mixing of Perl and Markup.

asp.NET I can't comment on. I didn't even know that you could use Perl in it.

mod_perl would be my preference. It keeps the Perl interpretor in memory, doesn't encourage you to mix Markup and Perl. It is also, as far as I know, used a lot more then ASP/PerlScript, so it is more mature and better supported.

Replies are listed 'Best First'.
Re^2: cgi and asp
by gellyfish (Monsignor) on Feb 21, 2005 at 11:50 UTC

    asp.NET I can't comment on. I didn't even know that you could use Perl in it.

    You can't unless someone provides a .NET CodeDom provider for Perl - I have a suspicion that this isn't going to happen any time real soon now :-|

    /J\

[reply]

      But of course you may use Perl with .Net, there's even Visual Perl - a plugin to MS Visual Studio.

      I never tried to write the ASP.Net pages themselves in Perl, though I'm pretty sure it's possible. I do use .Net DLLs implemented in Perl from C# on a few places though.

      Jenda
      We'd like to help you learn to help yourself
      Look around you, all you see are sympathetic eyes
      Stroll around the grounds until you feel at home
         -- P. Simon in Mrs. Robinson

[reply]

In Section Seekers of Perl Wisdom