I am currently evaluating the use of websockets asp.net to connect several thousand clients that will communicate with the application to a large extent 24x7, unless the server goes offline for repair, etc. Typically, expectations from the system are that web ports should not be disconnected unnecessarily, and clients will basically stay connected and ping the server every few minutes.
While I was exploring the viability of asp.net asp.net for our new architecture, I came across another stackoverflow message: IIS application pool cannot recycle when there is an open ASP.NET 4.5 Websocket , which apparently assumes that IIS does not recycle the pool. if there is an active connection to websocket. Is it by design, or did another person have an anomaly? If IIS processes the pool when it is actively connecting to the network, what is the expected behavior? Does Http.sys support connections, process the pool and things as if nothing had happened (from the client's point of view)? Should I just create a separate application pool for websites and disable its processing?
source
share