M.Erdmann Nov 24, 1999
Status: In Progress
This document contains the description of the ADCE architectur and the Client/Server architecture.
The ACDE architecture is based upon an client / server aproach where all information is stored on a central server. The server keeps track of all source components as they are requested by the clients. The commincation between client and server is done via an http-Server using cgi and http protocol.
The server will provide an view a global view on the repository of predefined components and a per project view for project specific parts.
From the client view, the ACDE will be integrated into the KDE desktop, which means all components are accessed via the html browser of the KDE and there will be some defintions for the ACDE applications running on the client localy, as i.e. the Systembuilder.
The user interface between client and the central repository is based upon the http protocol with cgi. All actions regarding the resository are send from the client to the server by means of html pages and cgi-commands. Files are transfered between work areas on the client and a sol called export area on the server by means of ftp.
In order to allow synchronous use of resources by multiple users a central server called administration server will be installed on a central system where all source texts is stored. The clients are able to access the server for a project to create, browse and update documents. For detailed description refere to the Administration Server (ADMS).
Clients like the repository browser do cummincate with the server by means of an textual command interface via a simple socket connection. The client is able to allocate a certain section for exclusive access. This means that the user which claims the section has the ability to update the section, while all other users are only able to access the sections as it was.
Main Index Contents