paulb@347 | 1 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
paulb@327 | 2 | <html xmlns="http://www.w3.org/1999/xhtml"> |
paulb@327 | 3 | <head> |
paulb@327 | 4 | <title>Anatomy of a WebStack Application</title> |
paulb@347 | 5 | <meta name="generator" |
paulb@347 | 6 | content="amaya 8.1a, see http://www.w3.org/Amaya/" /> |
paulb@328 | 7 | <link href="styles.css" rel="stylesheet" type="text/css" /> |
paulb@327 | 8 | </head> |
paulb@327 | 9 | <body> |
paulb@347 | 10 | <h1>Anatomy |
paulb@347 | 11 | of a WebStack |
paulb@347 | 12 | Application</h1> |
paulb@347 | 13 | <p>The simplest way to think of a |
paulb@347 | 14 | Web application is as just some code which |
paulb@347 | 15 | sits on a server and is sent messages - specifically HTTP requests - to |
paulb@347 | 16 | which it must respond by writing out messages to send back - |
paulb@347 | 17 | specifically HTTP responses. When using WebStack, we think of the |
paulb@347 | 18 | situation in terms of the following components:</p> |
paulb@347 | 19 | <table style="text-align: left; margin-left: auto; margin-right: auto;" |
paulb@347 | 20 | class="layers" border="1" cellpadding="5" cellspacing="0"> |
paulb@347 | 21 | <tbody> |
paulb@347 | 22 | <tr> |
paulb@347 | 23 | <th |
paulb@347 | 24 | style="text-align: center; background-color: rgb(255, 102, 102); vertical-align: middle;">Application |
paulb@347 | 25 | <span class="explanation">- |
paulb@347 | 26 | The application is described in this part of the documentation.</span> </th> |
paulb@347 | 27 | </tr> |
paulb@347 | 28 | <tr> |
paulb@347 | 29 | <th |
paulb@347 | 30 | style="background-color: rgb(255, 255, 102); text-align: center; vertical-align: middle;">Adapter |
paulb@347 | 31 | <span class="explanation">- |
paulb@347 | 32 | Adapters are explained in the <a href="deploying.html">deployment |
paulb@347 | 33 | documentation</a>.</span> </th> |
paulb@347 | 34 | </tr> |
paulb@347 | 35 | <tr> |
paulb@347 | 36 | <th |
paulb@347 | 37 | style="background-color: rgb(153, 153, 255); text-align: center; vertical-align: middle;">Server |
paulb@347 | 38 | environment <span class="explanation">- |
paulb@347 | 39 | Server environments are covered in the <a href="deploying.html">deployment |
paulb@347 | 40 | documentation</a>.</span> </th> |
paulb@347 | 41 | </tr> |
paulb@347 | 42 | </tbody> |
paulb@347 | 43 | </table> |
paulb@347 | 44 | <p>To get an application up and |
paulb@347 | 45 | running, this is what you have to do:</p> |
paulb@327 | 46 | <ol> |
paulb@347 | 47 | <li>Write some application code |
paulb@347 | 48 | which uses the WebStack API.</li> |
paulb@347 | 49 | <li>Write some simple adapter |
paulb@347 | 50 | code - this code "glues" the application to the environment that you |
paulb@347 | 51 | want to use.</li> |
paulb@327 | 52 | </ol> |
paulb@347 | 53 | <p>In this part of the |
paulb@347 | 54 | documentation, we will ignore the second |
paulb@347 | 55 | activity (it is covered in <a href="deploying.html">"Deploying a |
paulb@347 | 56 | WebStack |
paulb@347 | 57 | Application"</a>) and concentrate on the more important task of |
paulb@347 | 58 | defining an application's functionality with <a |
paulb@347 | 59 | href="simple-example.html">"A Very Simple Example"</a>.</p> |
paulb@327 | 60 | </body> |
paulb@327 | 61 | </html> |