Quote from MSDN about System.Web.HttpApplication

Quote from http://msdn.microsoft.com/en-us/library/4wt3wttw.aspx :

One instance of the HttpApplication class is used to handle many requests in its life. However, it can only process one request at a time. Thus, member variables can be used to store data for a query .

Why every request? Maybe for a set of queries? It seems that member variables can be used to store data during the full HttpApplication life cycle. Thus, the state of HttpApplication at the beginning of the second (for this HttpApplication request) is equal to the state at the end of the first (for this HttpApplication request).

Why do you need a request?

+3
source share
2 answers

, HttpApplication . , . HttpApplication.Application , , HttpApplication , ApplicationState, . HttpApplication , , . @Sidharth Panwar, concurrency, , , ( /), , IIS HttpApplication , . , (, , ).

+2

, IIS, HttpApplication ( -). HttpApplication ( global.asax) .

, , , HttpApplication . Asp.Net , concurrency .

, , , , , HttpApplication / Application . , Application, , .

, : P

P.S. BEST Asp.Net(http://www.west-wind.com/presentations/howaspnetworks/howaspnetworks.asp)

HttpApplication, .

0

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


All Articles