Compare commits

..

1 commit

Author SHA1 Message Date
4302d0332f Local addresses. 2025-04-30 01:23:22 +02:00

10
TODO.md
View file

@ -8,8 +8,7 @@ Modules should have their own specific API.
When a module currently requires to send messages, the API should reflect semantics instead of providing the module a way to just carry raw messages. When a module currently requires to send messages, the API should reflect semantics instead of providing the module a way to just carry raw messages.
For example, there are currently modules able to send messages (with a very simple `MessageToSend message` API), but instead of dealing with raw messages that need to be built inside the module, the API should be more semantic such as `ChangePassword new-password`. For example, there are currently modules able to send messages (with a very simple `MessageToSend message` API), but instead of dealing with raw messages that need to be built inside the module, the API should be more semantic such as `ChangePassword new-password`.
Once modules will have specific APIs, the entire state of the application could be moved into a single module (or *component*). Once modules will have specific APIs, the entire state of the application could be moved into a single module (or *component*) so every state modification can be handled in a single place.
Thus, every state modification can be handled in a single place.
Minor modifications: Minor modifications:
@ -18,11 +17,10 @@ Minor modifications:
# Features # Features
Delegation: About zone records:
- new RR record: the "delegation record", effectively removing all other RRs - allow '@' in record names (replaced by the fqdn, the "root" domain, such as "example.netlib.re.")
=> requires 2 nameservers - enable to change NS records, but after a accepting the consequences
- also enable to change NS records (but after a accepting the consequences)?
About the admin interface: About the admin interface: