From fe8bcdabd1ee214858f312fb155924d767606b78 Mon Sep 17 00:00:00 2001 From: Lars Wirzenius Date: Sun, 30 Dec 2018 19:18:37 +0200 Subject: Add: note about other UIs --- architecture.mdwn | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/architecture.mdwn b/architecture.mdwn index fccf309..5dd4b4d 100644 --- a/architecture.mdwn +++ b/architecture.mdwn @@ -25,13 +25,18 @@ The architecture has been designed under the following assumptions: Effireg consists of four main components: * **effiapi** provides a RESTful HTTP API for managing the membership - data, and for doing things with or to the data. All operations go - via the API. + data, and for doing things with or to the data. All operations on + the data go via the API. * **effiweb** provides the frontend for the web application to use the membership register. It renders HTML to the user, is accesses via a web browser, and generally is the user-visible part of Effireg. + Everything effiweb does, it does by using the effiapi API. If any + other user interfaces are added (say, mobile or command line), they + will be parallel to effiweb and will also use the effiapi API in the + same way as effiweb. + * **Qvisqve** provides authentication of end-users (the members, and admins). It lets users log in, and keeps track of what each user is allowed to do. -- cgit v1.2.1