From 706e7acbf8bc8157c1e43c740bff5c74191b7934 Mon Sep 17 00:00:00 2001 From: Ilya Kantor Date: Sat, 12 Sep 2020 15:57:10 +0300 Subject: [PATCH] minor fixes --- 5-network/10-long-polling/article.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/5-network/10-long-polling/article.md b/5-network/10-long-polling/article.md index b0e607e9..02d21d7a 100644 --- a/5-network/10-long-polling/article.md +++ b/5-network/10-long-polling/article.md @@ -70,11 +70,13 @@ As you can see, `subscribe` function makes a fetch, then waits for the response, ```warn header="Server should be ok with many pending connections" The server architecture must be able to work with many pending connections. -Certain server architectures run one process per connection; resulting in there being as many processes as there are connections, and each process will take a lot of memory. So, too many connections will just consume it all and thereby limiting the number of connections it can handle. +Certain server architectures run one process per connection; resulting in there being as many processes as there are connections, while each process consumes quite a bit of memory. So, too many connections will just consume it all. -That's often the case for backends written in languages like PHP and Ruby. However, technically this isn't a language issue, but rather an implementation one. Most modern languages allow to implement a proper backend, but some make it easier than others. +That's often the case for backends written in languages like PHP and Ruby. -Backends written using Node.js usually don't have such problems. +Servers written using Node.js usually don't have such problems. + +That said, it isn't a programming language issue. Most modern languages, including PHP and Ruby allow to implement a proper backend. Just please make sure that your server architecture works fine with many simultaneous connections. ``` ## Demo: a chat