dan
/
ricochet-go
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix README markup.

This commit is contained in:
Robin Burchell 2016-08-03 01:39:03 +02:00 committed by GitHub
parent ec680bad67
commit 5e08afa64f
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
README.md
View File

@ -4,21 +4,21 @@ The idea is to implement all client backend logic in Go, and export a RPC API fo
Benefits: 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 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 * 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**) * It's easy to build new frontends in anything that can use gRPC (like **cli**)
* Backends are headless and frontends are detachable and interchangable * Backends are headless and frontends are detachable and interchangable
* Can do some fancy sandboxing * Can do some fancy sandboxing
Other ideas: 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. * 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. * 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 * Can do frontend connection to backend over authorized onion for advanced setups
Structure: Structure:
* **core** is the client logic implementation * **core** is the client logic implementation
* **rpc** has gRPC/protobuf definitions & generated code * **rpc** has gRPC/protobuf definitions & generated code
* **backend** is the backend RPC server * **backend** is the backend RPC server
* **cli** is an example frontend client * **cli** is an example frontend client