Free web application server software for linux

LAMP Application Server project is a combination of common open source tools that provides a unified system from which administrators, developers, and other parties can manage a large application cluster. The underlying platform is LAMP based.
Enhancements:
- Fixed vhost config to correctly handle index pages on static directory area
- Fixed a MySQL install bug. Table `domain_dns_config` is now MyISAM like the rest.

SME Web Application Framework provides a Web application framework for small and medium-sized organizations.

SMEWebApp is a framework for constructing Web applications for SMEs (small and medium-sized enterprises, companies, institutions, and organizations). It is built on phpWebApp, and it is higher-level and more specific than phpWebApp.

It has some components that can be reused in any application (perhaps with small modifications), like hierarchical menus, user authentication, and user administration.

The aim of the project is to make Web application construction for SMEs easier than using VB.

Arkhon Web Application Framework provides an extremely lightweight, modular and extensible framework for developing scaleable community-based groupware applications through the PHP language.
Arkhon takes care of the following:
- Quick and intuitive skinning of your web application through the use of themes.
- Authentication and role based Authorisation
- Support for multiple database backend.
- Modular design.
- Extremely lightweight.
so that you can concentrate on the functionality of you web application.
Enhancements:
- Lots of refactoring of code (especially the API) in this release.
- It is ready for work to begin on the next phase (database backends).

Calyxo Web Application Framework encourages in MVC model 2 based web application development.

It offers support for true modular applications, i18n, a flexible view manager, a powerful validation engine, and more! Calyxo is entirely written in Java and builds on the latest Servlet and JSP technologies.

The Calyxo project divides into several components

Calyxo Base - this component collects some of the basic, reusable classes used throughout all the other components. It introduces basic concepts like modules, i18n, accessors and so on...

Calyxo Control - this component implements the Calyxo controller. Calyxo uses an approach similar to Struts here, so Struts users should feel familiar with Calyxo from the start. Calyxo Control may be considered as the "main part" of the Calyxo platform.

Calyxo Forms - this component allows the definition of forms, along with all their validation steps and lets you map inputs to properties of a data object. Complex validations, dependencies between inputs and mapping an input to a set of properties are supported. The Calyxo Forms JSP tag library provides replacements for HTML elements related to forms.

Calyxo Panels - this component allows the definition of pages in a container/component manner. Pages are dynamically composed from a tree of page fragments. Panel definitions may be nested to arbitrary depth and may use inheritance.

Calyxo Struts - this component focuses on integrating Calyxo parts into the very popular Apache Struts framework. The Calyxo Panels and Calyxo Forms components may be used with Struts to replace Struts Tiles and the Struts Validator.

CGI::Application is a framework for building reusable web-applications.

SYNOPSIS

# In "WebApp.pm"...
package WebApp;
use base CGI::Application;

# ( setup() can even be skipped for common cases. See docs below. )
sub setup {
my $self = shift;
$self->start_mode(mode1);
$self->mode_param(rm);
$self->run_modes(
mode1 => do_stuff,
mode2 => do_more_stuff,
mode3 => do_something_else
);
}
sub do_stuff { ... }
sub do_more_stuff { ... }
sub do_something_else { ... }
1;


### In "webapp.cgi"...
use WebApp;
my $webapp = WebApp->new();
$webapp->run();

CGI::Application is intended to make it easier to create sophisticated, high-performance, reusable web-based applications. This module implements a methodology which, if followed, will make your web software easier to design, easier to document, easier to write, and easier to evolve.

CGI::Application judiciously avoids employing technologies and techniques which would bind a developer to any one set of tools, operating system or web server.

OpenPlugin::Application is a subclass of CGI::Application, meant to help you create reusable web applications.

SYNOPSIS

# Example from OpenThoughts Demo.pm

package Demo;
use base "OpenPlugin::Application";
sub setup {
my $self = shift;
$self->run_modes(
mode1 => init_demo,
mode2 => get_os_list,
mode3 => get_os_info,
);
$self->start_mode( mode1 );
$self->mode_param(run_mode);
}
sub init_demo { ... }
sub get_os_list { ... }
sub get_os_info { ... }
1;

# Example from OpenThoughts demo.pl

#!/usr/bin/perl -wT
use strict;
my $r = shift;
my $demo = Demo->new( PARAMS => {
config => { src => "/path/to/OpenPlugin.conf" },
request => { apache => $r },
});

$demo->run();

OpenPlugin::Application is built on Jesse Erlbaums popular CGI::Application module. OpenPlugin::Application is simply a subclass of CGI::Application. Jesse says the following about CGI::Application:

"CGI::Application is intended to make it easier to create sophisticated, reusable web-based applications. This module implements a methodology which, if followed, will make your web software easier to design, easier to document, easier to write, and easier to evolve."

How does it do this? Jesse goes on to say:

"The guiding philosophy behind CGI::Application is that a web-based application can be organized into a specific set of "Run-Modes." Each Run-Mode is roughly analogous to a single screen (a form, some output, etc.). All the Run-Modes are managed by a single "Application Module" which is a Perl module. In your web servers document space there is an "Instance Script" which is called by the web server"

The biggest difference between CGI::Application and OpenPlugin::Application is that query object they both use; one is designed to use CGI.pm, the other OpenPlugin. Generally speaking, everything in the still applies. Any differences will be noted in this document.
It is not necessary to use OpenPlugin::Application in order to build web applications using OpenPlugin. This plugin is meant to be for your convenience -- to help you structure your web applications in a manner which makes sense, and is reusable.

WidgetServer is a component based Java/XML server-side GUI-framework which enables an application to run as either
- a monolithic application with a Swing GUI,
- a client/server application with a thin Swing client,
- or as an application with a rich Web client based on HTML and JavaScript
without any change and without loss of functionality!
WidgetServer gives you the choice if you develop a GUI either using
- HTML markup,
- a Java API like Swing,
- or XML markup.
XML markup helps to define an applications GUI fully separated from java code, Java code is useful for dynamic creation and modification during application runtime, while HTML markup is the best choice for typical web applications.
WidgetServer provides a unified component-based, object-oriented programming interface for Web and Swing GUIs to control and modify the GUI and to process events. The framework prevents from struggling with HTML, JavaScript and HTTP requests or from caring about the internals of Swing (e.g. Drag and Drop implementation).
For Swing client/server applications the framework cares for the client/server split as well as for the client/server communication including compression and security layers. Web applications are fully AJAX enabled while this feature remains fully configurable.
The framework also supports a mixed deployment mode, which enables one server to serve Swing clients and Web clients at the same time. The functionality of the Swing widget set is covered widely (and sometimes enhanced) in both (Swing and Web/HTML) client channels.
The project comes with a WYSIWYG GUI-builder which is completely build on the Wi.Ser-framework technology.
Enhancements:
- This version fixes some bugs in the JavaScript library.
- The Component-Set example is more interactive now.
- A new component similar to JSpinner has been added.
- A new package to create wizard based applications by declaration was added.
- Some enhanced error messages help to detect XML configuration errors now.