I know that long Comet polls are bad for web servers because they take up one thread for each connection. Thus, you cannot have many users with persistent connections or your web server will crash.
Is this the same with web sockets in HTML 5?
How can this solve the problem with the resource if it takes up one thread per persistent connection?
... because they take up one thread per connection
. . , . () IAsyncHttpHandler IIS .
Spender , - (, Apache mpm_worker mpm_prefork) / .
Comet Websockets ( ) - Proactor ( ), (). HTTP- keep-alive ( , - 99% ), /, Websockets.
Source: https://habr.com/ru/post/1758654/More articles:checking field values for null - stringCocoa Touch - Color of a round rectangular button? - cocoa-touchC ++ function template compiles the error "containerType is not a template" - c ++Что такое хороший способ форматировать sql-представление из MYSQL - code-formattingAndroid: How to get callback from content provider when data changes? - androidHow to generate a dynamic audio signal - c ++How an abstract (full-featured) long polling server works abstractly - httpWhat should be done in CodeIgniter models? - coding-styleКак создать пользовательский элемент управления Android и использовать его в Xml? - androidИгнорировать ошибки анализа HTMLAgilityPack? - c#All Articles