From a99254f7f7eb42379774d7e4055a35d2e8d5c9f8 Mon Sep 17 00:00:00 2001 From: joaquinelio Date: Sat, 22 Aug 2020 20:20:05 -0300 Subject: [PATCH 1/3] once in -> once every --- 5-network/10-long-polling/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/5-network/10-long-polling/article.md b/5-network/10-long-polling/article.md index 68eec844..b252fa9a 100644 --- a/5-network/10-long-polling/article.md +++ b/5-network/10-long-polling/article.md @@ -6,7 +6,7 @@ Being very easy to implement, it's also good enough in a lot of cases. ## Regular Polling -The simplest way to get new information from the server is periodic polling. That is, regular requests to the server: "Hello, I'm here, do you have any information for me?". For example, once in 10 seconds. +The simplest way to get new information from the server is periodic polling. That is, regular requests to the server: "Hello, I'm here, do you have any information for me?". For example, once every 10 seconds. In response, the server first takes a notice to itself that the client is online, and second - sends a packet of messages it got till that moment. From 938086674b24702d7d0b68398dece7db3598f9d7 Mon Sep 17 00:00:00 2001 From: joaquinelio Date: Sat, 22 Aug 2020 21:00:37 -0300 Subject: [PATCH 2/3] Update article.md --- 5-network/10-long-polling/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/5-network/10-long-polling/article.md b/5-network/10-long-polling/article.md index b252fa9a..bed7c798 100644 --- a/5-network/10-long-polling/article.md +++ b/5-network/10-long-polling/article.md @@ -70,7 +70,7 @@ 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 a process per connect. For many connections there will be as many processes, and each process takes a lot of memory. So many connections just consume it all. +Certain server architectures run one process per connect. So there will be as many processes as connections, and each process takes a lot of memory. Too many connections just will consume it all. That's often the case for backends written in PHP, Ruby languages, but technically isn't a language, but rather implementation issue. Most modern language allow to implement a proper backend, but some of them make it easier than the other. From 977cc0f92d246b81207cf0effce75dbbc7c3f8fa Mon Sep 17 00:00:00 2001 From: joaquinelio Date: Sat, 22 Aug 2020 21:20:03 -0300 Subject: [PATCH 3/3] Update article.md --- 5-network/10-long-polling/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/5-network/10-long-polling/article.md b/5-network/10-long-polling/article.md index bed7c798..0020b961 100644 --- a/5-network/10-long-polling/article.md +++ b/5-network/10-long-polling/article.md @@ -72,7 +72,7 @@ The server architecture must be able to work with many pending connections. Certain server architectures run one process per connect. So there will be as many processes as connections, and each process takes a lot of memory. Too many connections just will consume it all. -That's often the case for backends written in PHP, Ruby languages, but technically isn't a language, but rather implementation issue. Most modern language allow to implement a proper backend, but some of them make it easier than the other. +That's often the case for backends written in PHP, Ruby languages, but technically isn't a language issue, but rather implementation one. Most modern language allow to implement a proper backend, but some of them make it easier than others.. Backends written using Node.js usually don't have such problems. ```