webmcp

annotate doc/autodoc-header.htmlpart @ 388:29eeba26ff9f

find changesets by author, revision, files, or words in the commit message
Changed version number to 2.0.4
author jbe
date Wed Dec 02 09:37:47 2015 +0100 (2015-12-02)
parents cd9329b3bd78
children a7a335e2db93
rev   line source
jbe/bsw@0 1 <html>
jbe/bsw@0 2 <head>
jbe@381 3 <script type="text/javascript">
jbe@381 4 window.onload = function() {
jbe@381 5 if (window.location.hash) {
jbe@381 6 var encoded_hash = window.location.hash.replace(/^#/, '').replace(/_/g, '_USC_').replace(/\./g, '_DOT_').replace(/:/g, '_COL_');
jbe@381 7 var element = document.getElementById('autodoc_details_' + encoded_hash);
jbe@381 8 if (element) element.style.display = '';
jbe@381 9 }
jbe@381 10 }
jbe@381 11 </script>
jbe/bsw@0 12 <style>
jbe/bsw@0 13 body {
jbe/bsw@0 14 font-family: "Liberation Sans", sans-serif;
jbe/bsw@0 15 font-size: 11pt;
jbe/bsw@0 16 padding-bottom: 5ex;
jbe/bsw@0 17 }
jbe/bsw@0 18 .warning {
jbe/bsw@0 19 color: #ff0000;
jbe/bsw@0 20 }
jbe/bsw@0 21 h1, h2 {
jbe/bsw@0 22 font-family: "Liberation Serif", Georgia, serif;
jbe/bsw@0 23 }
jbe/bsw@0 24 h2 {
jbe/bsw@0 25 margin-bottom: 0.3ex;
jbe/bsw@0 26 }
jbe/bsw@0 27 p {
jbe/bsw@0 28 margin: 0px;
jbe/bsw@0 29 line-height: 130%;
jbe/bsw@0 30 }
jbe/bsw@0 31 tt, pre {
jbe/bsw@0 32 font-size: 10pt;
jbe/bsw@0 33 }
jbe/bsw@0 34 tt {
jbe/bsw@0 35 font-weight: bold;
jbe/bsw@0 36 white-space: nowrap;
jbe/bsw@0 37 }
jbe/bsw@0 38 .autodoc_entry {
jbe/bsw@0 39 margin-top: 1ex;
jbe/bsw@0 40 margin-bottom: 1ex;
jbe/bsw@0 41 }
jbe/bsw@0 42 .autodoc_comment_tail {
jbe/bsw@0 43 font-style: italic;
jbe/bsw@0 44 }
jbe/bsw@0 45 .autodoc_entry .short_synopsis {
jbe/bsw@0 46 cursor: pointer;
jbe/bsw@0 47 }
jbe/bsw@0 48 .autodoc_details {
jbe/bsw@0 49 padding-left: 1em;
jbe/bsw@0 50 padding-right: 1em;
jbe/bsw@0 51 border: 1px solid #777;
jbe/bsw@0 52 }
jbe/bsw@0 53 .autodoc_synopsis {
jbe/bsw@0 54 font-weight: bold;
jbe/bsw@0 55 }
jbe/bsw@0 56 .autodoc_synopsis .autodoc_comment_tail {
jbe/bsw@0 57 font-weight: normal;
jbe/bsw@0 58 color: #008000;
jbe/bsw@0 59 }
jbe/bsw@0 60 .autodoc_entry .autodoc_comment {
jbe/bsw@0 61 color: #400080;
jbe/bsw@0 62 }
jbe/bsw@0 63 .autodoc_source {
jbe/bsw@0 64 color: #505050;
jbe/bsw@0 65 }
jbe/bsw@0 66 </style>
jbe@388 67 <title>WebMCP 2.0.4 Documentation</title>
jbe/bsw@0 68 </head>
jbe/bsw@0 69 <body>
jbe@388 70 <h1>WebMCP 2.0.4 Documentation</h1>
jbe/bsw@0 71 <p>
jbe@278 72 WebMCP is a web development framework based on the Lua programming language (read more about Lua <a href="http://www.lua.org/about.html">here</a>).
jbe/bsw@0 73 </p>
jbe/bsw@0 74 <h2>Requirements</h2>
jbe/bsw@0 75 <p>
jbe@387 76 WebMCP has been developed on Linux and FreeBSD. Using it with Mac&nbsp;OS&nbsp;X is untested as of yet; Microsoft Windows is not supported. Beside the operating system, the only mandatory dependencies for WebMCP are the <a href="http://www.lua.org/">programming language Lua</a> version 5.2 or 5.3, the <a href="http://www.public-software-group.org/moonbridge">Moonbridge Network Server for Lua Applications</a> version 1.0.1 or higher, <a href="http://www.postgresql.org/">PostgreSQL</a> version 8.2 or higher, and a C compiler.
jbe/bsw@0 77 </p>
jbe/bsw@0 78 <h2>Installation</h2>
jbe/bsw@0 79 <p>
jbe@278 80 After downloading the tar.gz package, unpack it, enter the unpacked directory and type <tt>make</tt>. If you use Mac OS X or if you experience problems during compilation, you need to edit the <tt>Makefile.options</tt> file prior to compilation. The framework itself will be available in the <tt>framework/</tt> directory, while a demo application is available in the <tt>demo-app/</tt> directory. The <tt>framework.precompiled/</tt> and <tt>demo-app.precompiled/</tt> directories will contain a version with all Lua files being byte-code pre-compiled, which can be used instead. You may copy these directories (with <tt>cp -L</tt> to follow links) to any other place you like. Don't forget to setup a database, and make the <tt>tmp/</tt> directory of the application writable for the web server process. Good luck and have fun!
jbe@278 81 </p>
jbe@278 82 <h2>Configuration, pre-fork and post-fork initializers</h2>
jbe@278 83 <p>
jbe@278 84 The Moonbridge Network Server creates forks (i.e. clones) of the application server process in order to handle concurrent requests. Certain initializations may be performed before forking, other initializations must be performed after forking. The application's configuration files as well as its pre-fork initializers are executed before forking. The application's post-fork initializers are executed after forking. In particular, any libraries that open file or network handles during initialization must not be loaded before the server process is forked. Opening database connections must be performed after forking as well. Execution order is as follows:
jbe@278 85 </p>
jbe@278 86 <ol>
jbe@278 87 <li>
jbe@278 88 Loading all WebMCP libraries except the "multirand" library (multirand opens /dev/urandom and thus must not be loaded prior to forking)
jbe@278 89 </li>
jbe@278 90 <li>
jbe@278 91 Executing the selected configuration file: <tt>config/</tt><i>configuration_name</i><tt>.lua</tt>
jbe@278 92 </li>
jbe@278 93 <li>
jbe@278 94 Executing all pre-fork initializers (both those in the <tt>app/_prefork/</tt> and those in the <tt>app/</tt><i>application_name</i><tt>/_prefork/</tt> directory) until call of <tt>execute.inner()</tt> within each initializer
jbe@278 95 </li>
jbe@278 96 <li>
jbe@278 97 The Moonbridge Network Server forks the process (i.e. cloning the whole Lua machine)<br />
jbe@278 98 <span style="color: red">Note: no file handles or network connections must be opened prior to this point!</span>
jbe@278 99 </li>
jbe@278 100 <li>
jbe@281 101 Loading WebMCP's "multirand" library
jbe@281 102 </li>
jbe@281 103 <li>
jbe@278 104 Executing all post-fork initializers (both those in the <tt>app/_postfork/</tt> and those in the <tt>app/</tt><i>application_name</i><tt>/_postfork/</tt> directory) until call of <tt>execute.inner()</tt> within each initializer
jbe@278 105 </li>
jbe@278 106 <li>
jbe@278 107 For each request:
jbe@278 108 <ul>
jbe@278 109 <li>
jbe@278 110 Execution of all applicable filters until call of <tt>execute.inner()</tt> within each filter
jbe@278 111 </li>
jbe@278 112 <li>
jbe@278 113 Handling of the request by calling the appropriate view or action
jbe@278 114 </li>
jbe@278 115 <li>
jbe@278 116 Resuming execution of all filters in reverse order from that position where <tt>execute.inner()</tt> had been called
jbe@278 117 </li>
jbe@278 118 </ul>
jbe@278 119 </li>
jbe@278 120 <li>
jbe@278 121 Resuming execution of all post-fork initializers in reverse order from that position where <tt>execute.inner()</tt> had been called
jbe@278 122 </li>
jbe@278 123 <li>
jbe@278 124 Resuming execution of all pre-fork initializers in reverse order from that position where <tt>execute.inner()</tt> had been called
jbe@278 125 </li>
jbe@278 126 </ol>
jbe/bsw@0 127 </p>
jbe/bsw@0 128 <h2>Using the atom library</h2>
jbe/bsw@0 129 <p>
jbe/bsw@0 130 Lua itself has only very few built-in data types. The atom library gives support for extra data types. Currently the following extra data types are provided:
jbe/bsw@0 131 </p>
jbe/bsw@0 132 <ul>
jbe/bsw@0 133 <li>atom.fraction</li>
jbe/bsw@0 134 <li>atom.date</li>
jbe/bsw@0 135 <li>atom.time</li>
jbe/bsw@0 136 <li>atom.timestamp (date and time combined in one data type)</li>
jbe/bsw@0 137 </ul>
jbe/bsw@0 138 <p>
jbe/bsw@0 139 In addition the following pseudo-types are existent, corresponding to Lua's base types:
jbe/bsw@0 140 </p>
jbe/bsw@0 141 <ul>
jbe/bsw@0 142 <li>atom.boolean</li>
jbe/bsw@0 143 <li>atom.string</li>
jbe/bsw@0 144 <li>atom.integer</li>
jbe/bsw@0 145 <li>atom.number</li>
jbe/bsw@0 146 </ul>
jbe/bsw@0 147 <p>
jbe/bsw@0 148 Both atom.integer and atom.number refer to Lua's base type &ldquo;number&rdquo;.
jbe/bsw@0 149 </p>
jbe/bsw@0 150 <p>
jbe/bsw@0 151 New values of atom data types are created by either calling <tt>atom.<i>type</i>:load(string_representation)</tt> or by calling <tt>atom.<i>type</i>{...}</tt>, e.g. <tt>atom.date{year=1970, month=1, day=1}</tt>. You can dump any atom value as a string by calling <tt>atom.dump(value)</tt> and later reload it with <tt>atom.<i>type</i>:load(string)</tt>.
jbe/bsw@0 152 </p>
jbe/bsw@0 153 <h2>Using the Object-Relational Mapper &ldquo;mondelefant&rdquo;</h2>
jbe/bsw@0 154 <p>
jbe@278 155 The library &ldquo;mondelefant&rdquo; shipping with WebMCP can be used to access PostgreSQL databases. It also serves as an Object-Relational Mapper (ORM). The database connection is usually configured in the config file (e.g. in <tt>config/devel.lua</tt>):
jbe@278 156 </p>
jbe@278 157 <pre>
jbe@278 158 config.db = { engine="postgresql", dbname="webmcp_demo" }
jbe@278 159 config.db_trace = true</pre>
jbe@278 160 <p>
jbe@278 161 In addition to configuring the database, it must be opened within a post-fork initializer (e.g. in <tt>app/_postfork/01_database.lua</tt>):
jbe/bsw@0 162 </p>
jbe/bsw@0 163 <pre>
jbe@278 164 _G.db = assert(mondelefant.connect(config.db))
jbe@295 165 function mondelefant.class_prototype:get_db_conn() return db end</pre>
jbe/bsw@0 166 <p>
jbe@295 167 The parameters for <tt>mondelefant.connect</tt> are directly passed to PostgreSQL's client library libpq. See <a href="http://www.postgresql.org/docs/9.4/static/libpq-connect.html">PostgreSQL's documentation on PQconnect</a> for information about supported parameters.
jbe/bsw@0 168 </p>
jbe/bsw@0 169 <p>
jbe/bsw@0 170 To define a model to be used within a WebMCP application, create a file named with the name of the model and <tt>.lua</tt> as extension in the <tt>model/</tt> directory of your application. The most basic definition of a model (named &ldquo;movie&rdquo; in this example) is:
jbe/bsw@0 171 </p>
jbe/bsw@0 172 <pre>
jbe/bsw@0 173 Movie = mondelefant.new_class()
jbe/bsw@0 174 Movie.table = 'movie'</pre>
jbe/bsw@0 175 <p>
jbe/bsw@0 176 Note: Model classes are always written CamelCase, while the name of the file in <tt>model/</tt> is written lower_case.
jbe/bsw@0 177 </p>
jbe/bsw@0 178 <p>
jbe/bsw@0 179 To select objects from the database, the mondelefant library provides a selector framework:
jbe/bsw@0 180 </p>
jbe/bsw@0 181 <pre>
jbe/bsw@0 182 local s = Movie:new_selector()
jbe/bsw@0 183 s:add_where{ 'id = ?', param.get_id() }
jbe/bsw@0 184 s:single_object_mode() -- return single object instead of list
jbe/bsw@0 185 local movie = s:exec()</pre>
jbe/bsw@0 186 <p>
jbe/bsw@0 187 A short form of the above query would be:
jbe/bsw@0 188 </p>
jbe/bsw@0 189 <pre>
jbe/bsw@0 190 local movie = Movie:new_selector():add_where{ 'id = ?', param.get_id() }:single_object_mode():exec()</pre>
jbe/bsw@0 191 <p>
jbe/bsw@0 192 For more examples about how to use the model system, please take a look at the demo application.
jbe/bsw@0 193 </p>
jbe/bsw@0 194 <h2>The Model-View-Action (MVA) concept</h2>
jbe/bsw@0 195 <p>
jbe/bsw@0 196 As opposed to other web application frameworks, WebMCP does not use a Model-View-Controller (MVC) concept, but a Model-View-Action (MVA) concept.
jbe/bsw@0 197 </p>
jbe/bsw@0 198 <h3>Models</h3>
jbe/bsw@0 199 <p>
jbe/bsw@0 200 The models in MVA are like the models in MVC; they are used to access data stored in a relational database (PostgreSQL) in an object oriented way. They can also be used to provide methods for working with objects representing the database entries.
jbe/bsw@0 201 </p>
jbe/bsw@0 202 <h3>Views</h3>
jbe/bsw@0 203 <p>
jbe/bsw@0 204 The views in the MVA concept are different from the views in the MVC concept. As WebMCP has no controllers, the views are responsible for processing the GET/POST parameters from the webbrowser, fetching the data to be displayed, and creating the output by directly writing HTML to slots in a layout or by calling helper functions for the user interface.
jbe/bsw@0 205 </p>
jbe/bsw@0 206 <h3>Actions</h3>
jbe/bsw@0 207 <p>
jbe/bsw@0 208 Actions are similar to views, but supposed to change data in the database, hence only callable by HTTP POST requests. They are also responsible for processing the POST parameters from the webbrowser. They can modify the database, but instead of rendering a page to be displayed, they just return a status code. Depending on the status code there will be an internal forward or an HTTP 303 redirect to a view. When calling an action via a POST request, additional POST parameters, which are usually added by hidden form fields, determine the view to be displayed for each status code returned by the action.
jbe/bsw@0 209 </p>
jbe/bsw@0 210 <h2>Directory structure of a WebMCP application</h2>
jbe/bsw@0 211 <ul>
jbe/bsw@0 212 <li>
jbe/bsw@0 213 Base Directory
jbe/bsw@0 214 <ul>
jbe/bsw@0 215 <li>
jbe/bsw@0 216 <tt>app/</tt>
jbe/bsw@0 217 <ul>
jbe/bsw@0 218 <li>
jbe@278 219 <tt>_prefork/</tt>
jbe@278 220 <ul>
jbe@278 221 <li>
jbe@278 222 <tt>10_first_prefork_initializer.lua</tt>
jbe@278 223 </li>
jbe@278 224 <li>
jbe@278 225 <tt>30_third_prefork_initializer.lua</tt>
jbe@278 226 </li>
jbe@278 227 </ul>
jbe@278 228 </li>
jbe@278 229 <li>
jbe@278 230 <tt>_postfork/</tt>
jbe@278 231 <ul>
jbe@278 232 <li>
jbe@278 233 <tt>01_first_postfork_initializer.lua</tt>
jbe@278 234 </li>
jbe@278 235 <li>
jbe@278 236 <tt>03_third_postfork_initializer.lua</tt>
jbe@278 237 </li>
jbe@278 238 </ul>
jbe@278 239 </li>
jbe@278 240 <li>
jbe/bsw@0 241 <tt>main/</tt>
jbe/bsw@0 242 <ul>
jbe/bsw@0 243 <li>
jbe@278 244 <tt>_prefork/</tt>
jbe@278 245 <ul>
jbe@278 246 <li>
jbe@278 247 <tt>20_second_prefork_initializer.lua</tt>
jbe@278 248 </li>
jbe@278 249 </ul>
jbe@278 250 </li>
jbe@278 251 <li>
jbe@278 252 <tt>_postfork/</tt>
jbe@278 253 <ul>
jbe@278 254 <li>
jbe@278 255 <tt>02_second_postfork_initializer.lua</tt>
jbe@278 256 </li>
jbe@278 257 </ul>
jbe@278 258 </li>
jbe@278 259 <li>
jbe/bsw@0 260 <tt>_filter/</tt>
jbe/bsw@0 261 <ul>
jbe/bsw@0 262 <li>
jbe/bsw@0 263 <tt>10_first_filter.lua</tt>
jbe@278 264 </li>
jbe/bsw@0 265 <li>
jbe/bsw@0 266 <tt>30_third_filter.lua</tt>
jbe/bsw@0 267 </li>
jbe/bsw@0 268 <li>&hellip;</li>
jbe/bsw@0 269 </ul>
jbe/bsw@0 270 </li>
jbe/bsw@0 271 <li>
jbe/bsw@0 272 <tt>_filter_action/</tt>
jbe/bsw@0 273 <ul>
jbe/bsw@0 274 <li>
jbe/bsw@0 275 <tt>20_second_filter.lua</tt>
jbe/bsw@0 276 </li>
jbe/bsw@0 277 <li>&hellip;</li>
jbe/bsw@0 278 </ul>
jbe/bsw@0 279 </li>
jbe/bsw@0 280 <li>
jbe/bsw@0 281 <tt>_filter_view/</tt>
jbe/bsw@0 282 <ul>
jbe/bsw@0 283 <li>&hellip;</li>
jbe/bsw@0 284 </ul>
jbe/bsw@0 285 </li>
jbe/bsw@0 286 <li>
jbe/bsw@0 287 <tt>_layout/</tt>
jbe/bsw@0 288 <ul>
jbe/bsw@0 289 <li>&hellip;</li>
jbe/bsw@0 290 </ul>
jbe/bsw@0 291 </li>
jbe/bsw@0 292 <li>
jbe/bsw@0 293 <tt>index/</tt>
jbe/bsw@0 294 <ul>
jbe/bsw@0 295 <li>
jbe/bsw@0 296 <tt>_action/</tt>
jbe/bsw@0 297 <ul>
jbe/bsw@0 298 <li>
jbe/bsw@0 299 <i>action_name</i><tt>.lua</tt>
jbe/bsw@0 300 </li>
jbe/bsw@0 301 <li>
jbe/bsw@0 302 <i>another_action_name</i><tt>.lua</tt>
jbe/bsw@0 303 </li>
jbe/bsw@0 304 <li>&hellip;</li>
jbe/bsw@0 305 </ul>
jbe/bsw@0 306 </li>
jbe/bsw@0 307 <li>
jbe/bsw@0 308 <tt>index.lua</tt>
jbe/bsw@0 309 </li>
jbe/bsw@0 310 <li>
jbe/bsw@0 311 <i>other_view_name</i><tt>.lua</tt>
jbe/bsw@0 312 </li>
jbe/bsw@0 313 <li>&hellip;</li>
jbe/bsw@0 314 </ul>
jbe/bsw@0 315 </li>
jbe/bsw@0 316 <li>
jbe/bsw@0 317 <i>other_module_name</i><tt>/</tt>
jbe/bsw@0 318 <ul>
jbe/bsw@0 319 <li>&hellip;</li>
jbe/bsw@0 320 </ul>
jbe/bsw@0 321 </li>
jbe/bsw@0 322 </ul>
jbe/bsw@0 323 </li>
jbe/bsw@0 324 <li>
jbe/bsw@0 325 <i>other_application_name</i><tt>/</tt>
jbe/bsw@0 326 <ul>
jbe/bsw@0 327 <li>&hellip;</li>
jbe/bsw@0 328 </ul>
jbe/bsw@0 329 </li>
jbe/bsw@0 330 </ul>
jbe/bsw@0 331 </li>
jbe/bsw@0 332 <li>
jbe/bsw@0 333 <tt>config/</tt>
jbe/bsw@0 334 <ul>
jbe/bsw@0 335 <li>
jbe/bsw@0 336 <tt>development.lua</tt>
jbe/bsw@0 337 </li>
jbe/bsw@0 338 <li>
jbe/bsw@0 339 <tt>production.lua</tt>
jbe/bsw@0 340 <li>
jbe/bsw@0 341 <li>
jbe/bsw@0 342 <i>other_config_name</i><tt>.lua</tt>
jbe/bsw@0 343 </li>
jbe/bsw@0 344 <li>&hellip;</li>
jbe/bsw@0 345 </ul>
jbe/bsw@0 346 </li>
jbe/bsw@0 347 <li>
jbe/bsw@0 348 <tt>db/</tt>
jbe/bsw@0 349 <ul>
jbe/bsw@0 350 <li>
jbe/bsw@0 351 <tt>schema.sql</tt>
jbe/bsw@0 352 </li>
jbe/bsw@0 353 </ul>
jbe/bsw@0 354 </li>
jbe/bsw@0 355 <li>
jbe/bsw@0 356 <tt>locale/</tt>
jbe/bsw@0 357 <ul>
jbe/bsw@0 358 <li>
jbe/bsw@0 359 <tt>translations.de.lua</tt>
jbe/bsw@0 360 </li>
jbe/bsw@0 361 <li>
jbe/bsw@0 362 <tt>translations.en.lua</tt>
jbe/bsw@0 363 </li>
jbe/bsw@0 364 <li>
jbe/bsw@0 365 <tt>translations.</tt><i>languagecode</i><tt>.lua</tt>
jbe/bsw@0 366 </li>
jbe/bsw@0 367 <li>&hellip;</li>
jbe/bsw@0 368 </ul>
jbe/bsw@0 369 </li>
jbe/bsw@0 370 <li>
jbe/bsw@0 371 <tt>model/</tt>
jbe/bsw@0 372 <ul>
jbe/bsw@0 373 <li>
jbe/bsw@0 374 <i>model_name</i><tt>.lua</tt>
jbe/bsw@0 375 </li>
jbe/bsw@0 376 <li>
jbe/bsw@0 377 <i>another_model_name</i><tt>.lua</tt>
jbe/bsw@0 378 </li>
jbe/bsw@0 379 <li>&hellip;</li>
jbe/bsw@0 380 </ul>
jbe/bsw@0 381 </li>
jbe/bsw@0 382 <li>
jbe/bsw@0 383 <tt>static/</tt>
jbe/bsw@0 384 <ul>
jbe/bsw@0 385 <li>&hellip; (images, javascript, ...)</li>
jbe/bsw@0 386 </ul>
jbe/bsw@0 387 </li>
jbe/bsw@0 388 <li>
jbe/bsw@0 389 <tt>tmp/</tt> (writable by the web process)
jbe/bsw@0 390 </li>
jbe/bsw@0 391 </ul>
jbe/bsw@0 392 </li>
jbe/bsw@0 393 </ul>
jbe@278 394 <h2>Starting your application</h2>
jbe@278 395 <p>
jbe@278 396 Ensure that the <tt>moonbridge</tt> binary is within your system's search path and that the <tt>moonbridge_http.lua</tt> file is included in the LUA_PATH or linked into the framework's <tt>lib/</tt> directory (alternatively the MOONBR_LUA_PATH option might be set accordingly at compile-time of the Moonbridge Network Server). To start an application, call the <tt>mcp.lua</tt> executable (found in <tt>framework/bin/mcp.lua</tt>) with the following arguments:
jbe@278 397 </p>
jbe@278 398 <ol>
jbe@278 399 <li>
jbe@278 400 Path of the WebMCP framework directory, e.g. <tt>./framework</tt>
jbe@278 401 </li>
jbe@278 402 <li>
jbe@278 403 Path of your application's directory, e.g. <tt>./demo-app</tt>
jbe@278 404 </li>
jbe@278 405 <li>
jbe@278 406 Name of your applicaiton (usually <tt>main</tt>)
jbe@278 407 </li>
jbe@278 408 <li>
jbe@278 409 Name of configuration (e.g. <tt>devel</tt> to use config/devel.lua)
jbe@278 410 </li>
jbe@278 411 </ol>
jbe/bsw@0 412 <h2>Automatically generated reference for the WebMCP environment</h2>
jbe/bsw@0 413 <ul>

Impressum / About Us