From d522146de32f3238190822ce7f7261d9860e9426 Mon Sep 17 00:00:00 2001 From: Mattia Date: Fri, 13 Nov 2020 13:02:49 +0100 Subject: [PATCH] typo --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e9f5100..90ebdb3 100644 --- a/README.md +++ b/README.md @@ -26,7 +26,7 @@ One possible approach to achieve concurrency is to use threads, and despite thei actually might be a good choice when it comes to I/O for reasons that span far beyond the scope of this tutorial. If you choose to use threads, there are a couple things you can do, involving what is known as _thread synchronization primitives_ and _thread pools_, but once again that is beyond the purposes of this quickstart guide. -A library like giambio comes into play when you need to perform lots of [blocking operations](https://en.wikipedia.org/wiki/Blocking_(computing) +A library like giambio comes into play when you need to perform lots of [blocking operations](https://en.wikipedia.org/wiki/Blocking_(computing)) and network servers, among other things, happens to rely heavily on I/O which is a blocking operation. Starting to see where we're heading? @@ -288,4 +288,4 @@ if __name__ == "__main__": This is a relatively young project and it is looking for collaborators! It's not rocket science, but writing a proper framework like this implies some non-trivial issues that require proper and optimized solutions, so if you feel like you want to challenge yourself don't hesitate to contact me on [Telegram](https://telegram.me/isgiambyy) -or by [E-mail](mailto:hackhab@gmail.com) \ No newline at end of file +or by [E-mail](mailto:hackhab@gmail.com)