jeena/en.javascript.info
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

minor fixes

Browse source
This commit is contained in:
Ilya Kantor 2020-09-12 15:57:10 +03:00
parent a641a1a770
commit 706e7acbf8
1 changed files with 5 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

8
5-network/10-long-polling/article.md
View file

@ -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