DEVELOPMENT ENVIRONMENT

~liljamo/emerwen

35b93a575e79281e0291df876d4f11e3ab585e50 — Jonni Liljamo 12 days ago a10abbc
docs: update README.md
1 files changed, 12 insertions(+), 4 deletions(-)

M README.md
M README.md => README.md +12 -4
@@ 1,11 1,19 @@
# emerwen

## Handle?
    * Bad data in TCP stream? What would this do?
emerwen is a WIP host and service monitoring solution.

emerwen stands for *shepherdess* in Quenya.

It's architected as one Master server, which configures Workers who notify the
Master about the status of their targets.

gRPC is used for the Master<->Worker connection. A custom TCP protocol was
planned and experimented with, but scrapped due to *me* not having done it before
and not wanting to deal with the burden of managing all the connections manually etc, etc.
tldr: gRPC was easier lmao.

## Future
    * TLS for Master->Worker connection
        * https://github.com/rustls/tokio-rustls
    * TLS
    * Graceful shutdown for Workers when SIGINT is received
        * Send Master(s) a message that you're exiting, and wait for Master(s)
          to end the connection