Anatomy of a WebStack Application

The simplest way to think of a Web application is as just some code which sits on a server and is sent messages - specifically HTTP requests - to which it must respond by writing out messages to send back - specifically HTTP responses. When using WebStack, we think of the situation in terms of the following components:

Application - The application is described in this part of the documentation.
Adapter - Adapters are explained in the deployment documentation.
Server environment - Server environments are covered in the deployment documentation.

To get an application up and running, this is what you have to do:

  1. Write some application code which uses the WebStack API.
  2. Write some simple adapter code - this code "glues" the application to the environment that you want to use.

In this part of the documentation, we will ignore the second activity (it is covered in "Deploying a WebStack Application") and concentrate on the more important task of defining an application's functionality with "A Very Simple Example".