From b3c080cd633432b82227ac3adba5d2797a35aca6 Mon Sep 17 00:00:00 2001 From: Glutexo Date: Fri, 16 Aug 2024 20:00:09 +0200 Subject: [PATCH] Update description to match diagrams MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Operator-Downloader-Parser trinity became only a part of the whole architecture. It’s no longer true that Onigumo is composed of only three components. It wasn’t entirely true before either: there was still the idea of a Materializer. There are two flowcharts now. It’d be possible to call them a single one consisting of two parts, but clarity doesn’t harm. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 57d17c3..52d7336 100644 --- a/README.md +++ b/README.md @@ -6,13 +6,13 @@ Onigumo is yet another web-crawler. It “crawls” websites or webapps, storing ## Architecture ## -Onigumo is composed of three sequentially interconnected components: +The crawling part of Onigumo is composed of three sequentially interconnected components: * [the Operator](#operator), * [the Downloader](#downloader), * [the Parser](#parser). -The flowchart below illustrates the flow of data between those parts: +The flowcharts below illustrate the flow of data between those parts: ```mermaid flowchart LR