You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 5-network/10-long-polling/article.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,9 +70,9 @@ As you can see, `subscribe` function makes a fetch, then waits for the response,
70
70
```warn header="Server should be ok with many pending connections"
71
71
The server architecture must be able to work with many pending connections.
72
72
73
-
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.
73
+
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.
74
74
75
-
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..
75
+
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.
76
76
77
77
Backends written using Node.js usually don't have such problems.
0 commit comments