Книга: C# 2008 Programmer
How ASP.NET Works
How ASP.NET Works
When a web browser requests a page from a web server, the web server (IIS) first checks whether the request is for an HTML page. If it is, the request is filled by fetching the files from the hard drive and returning them to the client (web browser). If the client is requesting an ASP.NET page, IIS passes the request to the ASP.NET runtime, which then processes the application and returns the output to the client.
ASP.NET pages use the .aspx extension, which ensures that ASP.NET can run side by side with classic ASP, which uses the extension
One of the inherent problems with the HTTP protocol is its stateless nature. Put simply, a request made by a user is loaded into memory, fulfilled, and then unloaded. Subsequent requests by the same user are treated just like any other request; the server makes no attempt to remember what the user has previously requested. This stateless nature makes writing web applications a challenge because the application developer must explicitly devise mechanisms to enable the server to remember the previous state of the application. Several mechanisms have been devised over the years, including cookies and query strings for passing information to and from the server and the client.
In classic ASP, you typically need to write pages of code to preserve the state of the page after the user has posted a value back to the server. In ASP.NET, all of these mundane tasks (collectively known as state management) are accomplished by the ASP.NET runtime.
- What Do You Need to Run ASP.NET?
- Улучшенный протокол локальных соединений (XNET)
- How to read
- Chapter 9. How a rule is built
- Chapter 16. Commercial products based on Linux, iptables and netfilter
- How it was written
- How to plan an IP filter
- How to place proxies
- NETMAP target
- Internet Service Providers who use assigned IP addresses
- 7. AGGREGATION WITH INDEPENDENT WORKS