Let's take Spring web socket (with tomcat) for example.
Does Web Socket blocks thread while keeping the connection between server and client? (For example, connection can last 2-3 hours).
( Does web socket uses thread the same way as regular http request does (e.g., blocks/owns thread while performing the requests) )
Let's say server configured to have 200 threads in the thread pool and uses blocking io.
Does it mean that if we have 200 open long-living websocket connections, the server will not be able to handle other regular http requests or web socket connections while those 200 connections are open?
From tomcat docs (https://tomcat.apache.org/tomcat-8.5-doc/config/http.html):
The maximum number of request processing threads to be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled. If not specified, this attribute is set to 200. If an executor is associated with this connector, this attribute is ignored as the connector will execute tasks using the executor rather than an internal thread pool. Note that if an executor is configured any value set for this attribute will be recorded correctly but it will be reported (e.g. via JMX) as -1 to make clear that it is not used.
So this means that if we have 200 long-living web sockets, the server will not able to accept any requests anymore?
Then, if some web site has huge amount of users, and it needs to server at least 10000 users (which open WebSocket) simultaneously, does this means that it needs 50 servers only for those 10 000 users?
What about non-blocking io? (Netty, Akka http)