aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorToni Uhlig <matzeton@googlemail.com>2021-09-14 18:52:02 +0200
committerToni Uhlig <matzeton@googlemail.com>2021-09-14 18:54:33 +0200
commitc152e41cfb417eb586d9bb23049c4f70860f2ae3 (patch)
tree046126155fdb047007bdbce770b0a7d98333844c /README.md
parentaa89800ff996cec0305b1dde31e2dfb0a89c9bbc (diff)
README.md ascii update
Signed-off-by: Toni Uhlig <matzeton@googlemail.com>
Diffstat (limited to 'README.md')
-rw-r--r--README.md23
1 files changed, 10 insertions, 13 deletions
diff --git a/README.md b/README.md
index 3e03b52cf..83c1e14fe 100644
--- a/README.md
+++ b/README.md
@@ -21,21 +21,20 @@ Unfortunately nDPIsrvd does currently not support any encryption/authentication
This project uses some kind of microservice architecture.
```text
-_______________________ __________________________
-| "producer" | | "consumer" |
+ connect to UNIX socket connect to UNIX/TCP socket
+_______________________ | | __________________________
+| "producer" |___| |___| "consumer" |
|---------------------| _____________________________ |------------------------|
| | | nDPIsrvd | | |
-| nDPId --- Thread 1 >| ---> |> | <| <--- |< example/c-json-stdout |
-| (eth0) `- Thread 2 >| ---> |> collector | distributor <| <--- |________________________|
-| `- Thread N >| ---> |> >>> forward >>> <| <--- | |
+| nDPId --- Thread 1 >| ---> |> | <| ---> |< example/c-json-stdout |
+| (eth0) `- Thread 2 >| ---> |> collector | distributor <| ---> |________________________|
+| `- Thread N >| ---> |> >>> forward >>> <| ---> | |
|_____________________| ^ |____________|______________| ^ |< example/py-flow-info |
| | | | |________________________|
-| nDPId --- Thread 1 >| `- connect to UNIX socket | | |
-| (eth1) `- Thread 2 >| `- sends serialized data | |< example/... |
-| `- Thread N >| | |________________________|
-|_____________________| |
- `- connect to UNIX/TCP socket
- `- receives serialized data
+| nDPId --- Thread 1 >| `- send serialized data | | |
+| (eth1) `- Thread 2 >| | |< example/... |
+| `- Thread N >| receive serialized data -' |________________________|
+|_____________________|
```
It doesn't use a producer/consumer design pattern, so the wording is not precise.
@@ -54,8 +53,6 @@ All JSON strings sent need to be in the following format:
```
where `00015` describes the length of a **complete** JSON string.
-TODO: Describe data format via JSON schema.
-
# build (CMake)
```shell