Next: Requirements Up: The MX architecture and Previous: The MX architecture and

# Introduction

The MX architecture was designed to allow Cinema-MX (or other applications) to be extended straightforwardly and simply. This is achieved by splitting the application up into a series of small modules. These modules can then be put together to form the end application.

For the Cinema-MX application as well as allowing modularity we wanted to gain extensibility, allowing the user to integrate new modules into Cinema-MX, without requiring alteration of the main code base. To this end, XML has been used to define which modules should be loaded, and also to provide some configuration for these modules if required.

In the following documentation I describe how the MX architecture works and what all the various bits do. If you can't be bothered to read this, then there is a very quick ``step-by-step'' guide in Section 7, which you might prefer.