Code

Below are links to the various Languages under which you will find one or more web application technology platforms. If you framework/platform of choice is not listed it is because we determined that it was not the leading framework in the particular technology platform. This was determined by consensus of the authors plus the advice of our advisor for each particular technology platform.

• Ruby
• Python
• PHP
• .NET
• Java
• ColdFusion
• Perl
• Groovy

HTML Prototypes

The following HTML prototypes were used as the starting point for any screencast. Step 1 of each screencast is to "import" the HTML into your project.I have provided these as zip files of the public_html directory. Additionally, in the second and third profiles you will find the sql scripts you will need to create or modify the database respectively.

1. Profile 1 or SimpleWebApp.zip or you can view the HTML Prototype please remember this is an PROTOTYPE! Not all links function because your supposed to make them function.
2. Profile 2 or ThreeTierWebApp.zip or you can view the HTML Prototype please remember this is an PROTOTYPE! Not all links function because your supposed to make them function.
3. Profile 3 or EnterpriseWebApp.zip or you can view the HTML Prototype please remember this is an PROTOTYPE! Not all links function because your supposed to make them function.

Out of Scope

The following areas and items are out of scope for the purpose of this research:

• We will be performing all of our performance testing on the same hardware. We will initially test all the applications on MS Windows Advanced Server 2003, as ASP.net will not run on any other operating system. We will additionally test all but ASP.net platform on a standard Linux distribution to avoid any windows specific platform problems. Most of the platforms are typically not run on Windows, but to be fair to windows we need to compare all on the same OS. We will use the same hardware and a standard OS image to avoid any inconsistencies. Please note that IIS will be used for ASP.net and Apache will be used for the other platforms. This disparity cannot be avoided due to the limitations of ASP.net.
• We have selected MySQL for all platforms to use for their relational database. We are not going to use object databases or compare performance against particular branded databases. It is assumed that MySQL represents a relational database that is accessible for all the possible platforms and is generally SQL compliant.
• Commercial or Open source products that run on top of one or more of the evaluated platforms and generate static or client side dynamic web functionality, such as content management systems, web publishing tools, or eCommerce systems. This includes applications like Drupal, Plone, Joomla, Alfresco, Cozmos et al…
• Some third party libraries may be commonly used with various platforms. These libraries will be explicitly called out in the screencasts and instructions. The definition of a library will be defined as any library that is acquired and the source is not modified. If the source has to be modified in any fashion, then all lines of code in that group of files will be counted towards your lines of code count. E.G. it’s cheating to grab code samples from the web without explicitly calling them out or typing them in as part of the screencast, if it doesn’t come in a library it counts as code that is written. We assume that if you modify the library of code in any fashion then you are taking ownership of that code base and future maintenance. We are not trying to explicitly compare how many code snippets exist out in the world to solve a particular problem. In addition, if the library is a commercial library then the cost must be reported as part of the results.
• Any third party application service provider. We assume that these web applications themselves are based on one of the application platforms we are evaluating. eBay/Paypal, Yahoo Stores, Google Cart, Amazon zShops, Blogger, Myspace, Livejournal, Salesforce, etc…
• Client side publishing tools that generate static website content such as MS Front Page, Adobe Dreamweaver, and MS Word.
• Products and platforms that deliver interactive browser functionality, regardless of their ability to call back to one of the application platforms that is being investigated. It is assumed that any of the web application technology platforms could be used to support the server side functionality of an application front end built with these technologies. Examples: Sun Java Applets, AJAX, MS ActiveX Controls, Adobe Flash, Apple Quicktime, Adobe Acrobat, Adobe Flex et al…