How User Request Reaches To Active Server Pages
The scripting technology used to make decisions about how to handle the request, and the Web server itself. Before you can understand much about what the ASP engine can do, you need to know what happens before the request of user reaches the code in your ASP page.
A web request requires two components: a web server and a client. The client is usually a browser, but could be another type of program such as a spider or an agent. The server and the browser are usually on two separate computers, but that is not a requirement. You can use a browser to request pages from a Web server running on the same computer. The point is that whether the Web server and the browser are on the same computer or whether they are on opposite sides of the world, the request worlds almost exactly the same way. Both the server and the client must use a defined protocol to communicate with each other.
A protocol is simply an agreed – upon method for initiating a communications session, passing information back and forth, and terminating the session. There are several protocols used for web communications: the most common are Hypertext transfer Protocol used, Web request are carried over an underlying network protocol called Transmission Control Protocol / Internet Protocol, which is global communications standard that determines the rules two computers follow when they exchange information. The server computer runs an endless loop to check for communications initialization. The client sends an initialization to begin a session. The initialization is a defined series of bytes. The byte content is not important the only important thing is that both computes recognize the byte series as an initialization. When the server receives the initialization request, it acknowledges the transmission by returning another series of use in the back and forth manner. If computer spoke in words, you can imagine the conversation being conducted.
TCP/IP is only one of many computer communication protocols, but due to the popularity of the internet, it has become ubiquitous. You would not need to know much than that about TCP/IP to use it – the underlying protocol is almost entirely transparent. You do, however, need to know how one machine finds another machine to initiate a communications session. How a Client Request Content? When you type a request into the browser address bar or click a hyperlink, the browser packages the requests and sends it to a naming server. The naming server maintains a database of names, each of which is associated with an IP address. Computers do not understand words very well, so the naming server translates the requested address into a number. The text name you see in the link or the address bar is actually a human friendly version of an IP address.
The IP address is a set of four numbers between 0 and 255, separated by periods. Each IP address uniquely identifies a single computer. If the first naming server does not have the requested address in its database, it forwards the request to a naming server further up the hierarchy. Eventually, if no naming server can translate the requested name to an IP address, the request reaches one of the powerful naming server that maintain master list of all publicly registered IP addresses. If no naming server can translate the address, the failed response travels back through the naming server hierarchy until it reaches your browser.
For more information visit to- Website Designing Service And Website Designer
Processing your request, Please wait....
