From e41e665f0c79ad5468f1175db8cd9b51b032b1e9 Mon Sep 17 00:00:00 2001 From: Dimitri Staessens Date: Fri, 19 Feb 2021 17:47:50 +0100 Subject: Remove Intro --- content/en/docs/Overview/_index.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'content/en/docs/Overview') diff --git a/content/en/docs/Overview/_index.md b/content/en/docs/Overview/_index.md index 9e648b0..00d0467 100644 --- a/content/en/docs/Overview/_index.md +++ b/content/en/docs/Overview/_index.md @@ -79,10 +79,13 @@ accessible on [arXiv](https://arxiv.org/pdf/2001.09707.pdf). The best place to start understanding a bit what Ouroboros aims to do and how it differs from other packet networks is to first watch this -presentation at -[FOSDEM 2018](https://archive.fosdem.org/2018/schedule/event/ipc/) -but note that this presentation is over three years old, and -very outdated in terms of what has been implemented. +presentation at [FOSDEM +2018](https://archive.fosdem.org/2018/schedule/event/ipc/) but note +that this presentation is over three years old, and very outdated in +terms of what has been implemented. The prototype implementation is +now capable of asynchronous flows handling, doing retransmission, flow +control, congestion control... + The next things to do are to have a quick read of the [flow allocation](/docs/concepts/fa/) and -- cgit v1.2.3