The strength of the AP software-environment lies in a consequent and all out support of completely independent software components. The number of components that can be handled by the system is unlimited. This is made possible by a very compact piece of software, The Activator (35K-100K depending). Derived from the runtime circumstances of the application, a set of components is identified and combined. This way, AP “applications”, called “Assemblies” are born on the spot. The AP technology enables the dynamic replacement or addition of components to an Assembly (true software hot swapping).

We chose not to introduce a new programming language. The base environment is programmed in “C” but other languages can be used to program components. Programming can also be done around legacy code, the AP software is non-intrusive. This enables the “componentisation” of legacy applications, and thus brings them the same advantages as regular components. This way software with ‘history’ does not have to be rewritten or thrown away.

As said AP Applications are called Assemblies. The AP component technology makes away with the present form of applications (executables + libraries) and as a consequence with the problems related to these formats, especially those related to runtime software manageability. (e.g. DLL hell, huge applications, …)