Tue Jun 30 16:35:08 EDT 2020
Redo as a composition layer
It actually works quite well: leave the components to their protocols.
Let them do whatever makes sense. Files are probably best. Then
orchestrate a dataflow network around that.
It is a bit of work to capture all that in data structures and build
rules, but that work needs to happen anyway, so maybe best to use a
good structure for it.
One thing though: I am tired of dynamic typing errors. It would
probably be a good idea to rewrite this in Haskell or something, or to
create a layer where everyting is actually proxied in the file system
using some kind of tokens, such that ordinary build tools can be used?
E.g. a running daemon could be a file with its address (pid, socket,