[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ next ]

Webapps Policy Manual
Chapter 2 - Terms and Conventions

httpd and web-server

Any server providing content via the Hyper Text Transfer Protocol.

Web application

A suite of static and dynamic content, as well as any other associated scripts and data serving a common purpose.

Static content

Read-only content served without requiring server interpretation or execution.

Dynamically interpreted content

Architecture-independant content requiring server interpretation. Most PHP applications are based on this type of content.

Dynamically executed content

Similar to interpreted content, but instead of requiring the server to interpret the underlying file(s), content is obtained by execution of a script or binary. Most packages using a "cgi-bin" would fall under this category.

Cached content

Content that can be reconstituted from existing data, such as proxied data or graph images generated from databases.

Include files

Architecture-independant files referenced by dynamic content providing functionality but not directly accessed from the web.

Include libraries

The subset of include files intended for site wide use by multiple applications.

Document root or web root

The base directory underneath which web content is accessed. This sometimes will refer to the "global" document root (parent directory for entire web site), and sometimes refer to an "application" document root, which is the root directory specific to an application.


generally speaking, the name of the package containing the web application. however, it can also be expanded to include names of other packages (or virtual packages) generated by the same source package, or other commonly acceptable variations on said package names.

[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ next ]

Webapps Policy Manual

Revision: DRAFT-1.10

Alexis Sukrieh
Pascal Hakim
Neil McGovern
Sean Finney
Joey Schulze