From 7cb10f5814837228ba95402464cd6769dea249a1 Mon Sep 17 00:00:00 2001 From: Philippe PITTOLI Date: Sat, 1 Jun 2024 01:41:28 +0200 Subject: [PATCH] Blah. --- paper/paper.ms | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/paper/paper.ms b/paper/paper.ms index 63282a4..1bc5d2b 100644 --- a/paper/paper.ms +++ b/paper/paper.ms @@ -1045,11 +1045,15 @@ wget "https://netlib.re/token-update/" .SOURCE .B "The technical parts" . -The service is split into two main components: a user interface (website written in purescript) and a daemon (dnsmanagerd) handling all the server operations. -Several "databases" are maintained +The service is split into two three components: a user interface (the website, written in purescript), an authentication daemon (\fIauthd\f[]) and a daemon handling all the server operations related to the actual service (\fIdnsmanagerd\f[]). +Several "databases" are maintained: +.ENUM \fIusers\f[], +.ENUM \fIdomains\f[], +.ENUM \fItokens\f[], +.ENUM \fIconnected users\f[] for collaborative work +.ENDENUM .BULLET Common and RAM-only databases -.BULLET database: users, domains, tokens, connected users (for collaborative work) .ENDBULLET Performance-wise, netlibre handles between 2 to 3k req/s with a single core, without any optimization.