Details about the construction of this webpage

The EU Cookie directive requires all websites hosted in the EU to declare their cookie usage on each page that uses them. This area contains information about how cookies are used, and also information about how other systems are used in the construction of this web page.

Cookie Usage

The content using Cookies on this page is:
  • 'Google Analytics' * may be using Analytical cookies.
*May be using cookies - since this content is hosted by a third party, we can not give details on their cookie usage.
For more information about Cookies on this site please visit the Cookie and Privacy Page
Note: This cookie usage is specific to the current page, other pages on this site may be using cookies for other purposes.

JavaScript Usage

This page also relies on JavaScript to create the interactive content on this page. If JavaScript is disabled, a plain non-interactive page will be available.

HTML Usage

This page is natively HTML 4.01 Transitional, but uses some HTML5 and CSS3 elements to enhance the experience on browsers that support them. Browsers that can not support the features should still provide the content, but may lack some styles and effects newer browsers can offer.


There is an automatic failsafe that renders a plain HTML page if JavaScript is disabled, or if the page takes longer than a few seconds to render. If an issue occurs and you are unable to get a page to view, please contact the web master.
The Marlowe test Logo

The Marlowe Online Server - WEB Interface

The WEB Software

Building websites with ease

About the WEB Software

The WEB Software runs in two parts, the server side uses a compiled C WEB Application which delivers raw content to Apache requests. The client side uses JavaScript to create the webpage from the raw content.

The Server Side

The WEB Application is responsible for deciding the resources required by the page, and including them (either as inline content, or setting a reference for further calls). It also compresses content on the fly.

The WEB Application is also 100% responsible for security. It handles all of the inbound calls to the server (including those for images and other resources).

The WEB Application is extremely security focused, with most of the code devoted to determining the security level, and deciding the correct response.

The WEB Application is backed by several C libraries that provide different areas of functionality to the Application. These libraries are created and managed internally and are a part of the WEB Application.

The Client Side

The JavaScript on the client side is referenced by the WEB Application. This also adds the raw data required to build the webpage.

The WEB JavaScript heavily uses the separate Marlowe Packages Library, which is a collection of smaller Libraries all using the Packages name space.

The WEB Application client side uses the raw data and generates the webpage on the client machine, this saves a serious overhead on the server and also allows for a far richer and more interactive web page.

The Marlowe Packages Library

This was original part of the WEB Application, but after WEBv3, the library was completely separated into its own area. The Library does not need the WEB Application, and can be used entirely independently via its own BootLoader library - this loads the Library, and starts the Application that is using it.

Currently the library has been used with a number of stand alone application, test applications, and some demonstration Smart Phone applications using existing Smart Phone App JavaScript Frameworks.

The Marlowe Packages Library provides:
Packages name space
Built in Patterns, such as Singleton
Built in code documenter
User Interface tools, menus, tabs
Interactive Form Class
Limited Rich Text Editor
Advanced Mathematical Operations, including Trig
HTML manipulation
XCSV/CSV file manipulation
XML parsing and creation
Multiple 'fancy' effects for Image Galleries / Pop ups etc
All of the above is original code.

Currently the Marlowe Packages Library is not freely available. Before the library could be released the following measures need to be taken to ensure the code is modifiable and expandable in the future:
Change all API methods to include expandable (optional) arguments, so that additional arguments can be added in the future.
Comment reviews - although most should be up to date.
Documenter thoroughly checked to ensure it works perfectly.
Code review.

The Marlowe Online Server WEB Interface



Hosted by the Marlowe Online Server WEB Interface