Both AppServ and WebDev suppport server side scripting. To maintain the most stable environment possible, users must do all script editing (not static HTML editing) and script development on WebDev. Once the script has been fully tested, users can move the script to AppServ. This way, AppServ should be fairly stable; however WebDev will be prone to crashes and other problems due to script errors. This instability is unavoidable. It is imperative that users do all script editing and testing on WebDev. If a users script crashes AppServ or causes other serious problems, we will be forced to disable or remove his/her scripts and/or account.
Username and passwords will be the same for all three machines.
WWW will continue to be the primary web server for all non-scripted web content. AppServ should only be used for scripted pages, thus no static content (basic HTML pages) should be kept on it. Users will continue to use WWW as their primary site address and for the majority of their content, and simply link to any scripts they might need on AppServ.
All three web servers (WWW, AppServ and WebDev) support the following connectivity:
AppServ and WebDev support the following types of scripting and/or languages:
PHP is a scripting language similar to ASP; however, PHP is both the technology and the language. PHP pages must have the .php extension. The PHP language syntax is very similar to the C and Perl programming languages. For help on using PHP, you can go to the following sites:
Perl is a scripting language that cannot be embedded in an HTML file. Perl scripts are generally used to accept web page form results and generate response pages, e-mail users, etc. All Perl scripts must have the .pl extension. Perl is extremely powerful and flexible, but the language can be very difficult for users to learn. For help on using Perl, you can go to the following sites:
Server Parsed HTML (or Server Side Includes/SSI) allow for referencing other web pages/scripts from within an HTML page as well as calling external programs and referencing system variables. All Server Parsed HTML files must have the .shtml, .stm, or .shtm extension. Common uses of SHTML are including the output of a Perl script, discovering the type of browser the remote user has, etc. For help on SHTML, you can go to the following sites:
Subscribe to RSS headline updates from: