Reusing application pool after "Fixed number of requests"

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)?

+3
source share
2 answers

, , . aspx, , , , , ( .Net) , . Session, Application . asp php, .

. , . , , IIS6 15 , , , , .

+4

. - , . , - - , HTTP.

+3

Source: https://habr.com/ru/post/1709902/


All Articles