summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2018-12-30 19:18:37 +0200
committerLars Wirzenius <liw@liw.fi>2018-12-30 19:18:37 +0200
commitfe8bcdabd1ee214858f312fb155924d767606b78 (patch)
tree45d7ec018e6ebb89b4664eeba7203fdf48ead53f
parent2e77bf3a23bf578b5f4e989d26a1f53e2ceea5f2 (diff)
downloadeffireg-website-fe8bcdabd1ee214858f312fb155924d767606b78.tar.gz
Add: note about other UIs
-rw-r--r--architecture.mdwn9
1 files 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.