What are the implications of setting up the IIS application pool for re-processing after the "Number of requests fixed"?
Suppose this number is 100, and the 99th person connects to my website, then the 100th person comes in and starts restarting the application pool.
Does this mean that all session information for sessions 1-99 will be lost (the session in the process expires when the application pool worker process restarts)?
, , . aspx, , , , , ( .Net) , . Session, Application . asp php, .
. , . , , IIS6 15 , , , , .
. - , . , - - , HTTP.
Source: https://habr.com/ru/post/1709902/More articles:Delphi 7 continues to use obsolete form - formsSystem Boot Definition - windowsHas anyone been able to debug classic asp code with visual studio 2005 or later? - debuggingDoes the HOWTO transfer the request made by the Apache server to the IIS server without using URL redirection? - redirectHow to count the number of pages in a Microsoft Word file using Ruby? - ruby | fooobar.comThe safest way to remove unwanted spaces - javascriptError creating pch file with CPP definitions - gccSplit CSV String - stringWhat is the name of this design pattern? - design-patternsFor two methods to call each other: how to prevent an infinite loop? - javaAll Articles