From 5e08afa64faf396c7fe2942a9deb1cd256d7e9a8 Mon Sep 17 00:00:00 2001 From: Robin Burchell Date: Wed, 3 Aug 2016 01:39:03 +0200 Subject: [PATCH] Fix README markup. --- README.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/README.md b/README.md index d4a00b1..5ebb373 100644 --- a/README.md +++ b/README.md @@ -4,21 +4,21 @@ The idea is to implement all client backend logic in Go, and export a RPC API fo Benefits: - * We can have all network-facing and critical logic in Go, without being forced to use Go for frontends (because it lacks decent UI capability) - * We can keep the current Qt UI implementation as one frontend - * It's easy to build new frontends in anything that can use gRPC (like **cli**) - * Backends are headless and frontends are detachable and interchangable - * Can do some fancy sandboxing +* We can have all network-facing and critical logic in Go, without being forced to use Go for frontends (because it lacks decent UI capability) +* We can keep the current Qt UI implementation as one frontend +* It's easy to build new frontends in anything that can use gRPC (like **cli**) +* Backends are headless and frontends are detachable and interchangable +* Can do some fancy sandboxing Other ideas: - * This is currently using RPC only for the backend<->frontend; would it make sense to RPC any other layers or distinct components? Could have security benefits. - * In particular, we still have one process that has access to private keys, tor config, and untrusted network traffic. That sucks. - * Can do frontend connection to backend over authorized onion for advanced setups +* This is currently using RPC only for the backend<->frontend; would it make sense to RPC any other layers or distinct components? Could have security benefits. +* In particular, we still have one process that has access to private keys, tor config, and untrusted network traffic. That sucks. +* Can do frontend connection to backend over authorized onion for advanced setups Structure: - * **core** is the client logic implementation - * **rpc** has gRPC/protobuf definitions & generated code - * **backend** is the backend RPC server - * **cli** is an example frontend client +* **core** is the client logic implementation +* **rpc** has gRPC/protobuf definitions & generated code +* **backend** is the backend RPC server +* **cli** is an example frontend client