Steven: > I am keen to use Apache::ASP but am unsure as to what > benefits it has over CGI programming. Can anyone argue the > case for me?
In my own mind, it greatly depends on the skill level of your CGI programming. Since Apache::ASP is built primarily on mod_perl and other existing Apache interfaces, it doesn't offer much in the way of "new features." On the other hand, using many of these interfaces requires a signficant level of expertise, increasing the level of training necessary when bringing new people onto your web development team. Apache::ASP repackages the various web APIs into consistent, logical, and modular way. It promotes maintainabilty and modularity. The concept of a "web application" and it's associated objects and events is easy to understand. And it (with some restrictions) allows the writing of "portable" web code between IIS and Apache servers. My two favorite Apache::ASP features include: The ASP object model (including the $Application, $Session, $Server, $Request and $Response objects), and the $Response->Include model for turning .htm files into subroutines. Why Apache::ASP over mod_php? Simple: perl. Anything that can be done in perl, or any code that has already been written can be incorporated into an Apache::ASP application. The downside? Many people are jumping on the PHP bandwagon (for a variety of good reasons) so if you are looking for people to work in your shop, it will be easier to find PHP web developers. Hope this helps. JL --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
