Product Description

A Web server is a program that uses HTTP (Hypertext Transfer Protocol) to serve the files that form Web pages to users, in response to their requests, which are forward by their computers’ HTTP clients. Dedicate computers and appliances may be refer to as Web servers as well. Modern web application development frameworks such as ASP.NET and its three flavors (Web Forms, MVC, and Web Pages) and non-Microsoft products such as Ruby on Rails all sit firmly between the web server and you, the web application builder. In the Microsoft world, we’re use to working with IIS,10 whereas in the Unix world, Apache11 and Nginx12 are commonly used. ASP.NET MVC targets developers who are interested in patterns and principles like test-driven development, separation of concerns, inversion of control (IoC), and dependency injection (DI).

With ASP.NET MVC, you can have multiple teams working on a web site because the code for the business logic is separate from the code and markup for the presentation layer—developers can work on the business logic while designers work on the markup and JavaScript that is sent to the browser. ASP.NET is a unified Web development model that includes the services necessary for you to build enterprise-class Web applications with a minimum of coding.In other words, serving content to a browser actually involves three pieces:

1. The web server (managing workers, also known as threads), and possibly handling upfront things like white lists and black lists.
2. Based on the request syntax, processing that request into meaningful entities such as session state and routing.
3. The application-specific response to a route, an authentication request, and so forth.

Table of Contents:

1:Introduction
2:Source Code
3:Why Build a Web Server?
4:Your First Web Server
5:Threads, Tasks, and Async/Await
6:Thread-Spanning Workflows
7:Routing
8:Sessions
9:HTTPS
10:Error Handling and Redirecting
11:Parameterized Routes
12:Form Parameters and AJAX
13:View Engines
14:Stress Testing
15:Conclusion