Architectural Whitepaper

Dag-Erling Smørgrav

January 19th, 2002

Table of Contents

1. Introduction
2. The core library
2.1. Data handling
2.1.1. Atoms
2.1.2. Contexts
2.2. Security model
2.3. Primitives
2.3.1. Reports
2.3.2. Transactions
2.4. Dialogs
3. The dialog drivers
3.1. The Servlet driver
3.2. The Swing driver
4. Applications
4.1. The address database
4.2. The task manager
5. Tools
5.1. The dialog composer
5.2. The SQL designer

This article describes the overall architecture of the Convention Database project.

Lorem ipsum dolor sit amet...

This document is a work in progress!

Since dialogs are a mostly abstract concept, some interface code is necesasry to actually present information to the user and obtain the required input.

The foundation for these drivers is the Conversation interface, which declares an API for constructing a page (by setting its title and adding text, inputs and actions to it), presenting a page to the user, and registering a listener that will be notified when the user has filled out the form and selected one of the actions.

These are convenient tools that are not strictly required for the operation and maintenance of the Convention Database, but facilitate certain common tasks.