Scribd
Upload
73 views

Data Transfer Over The Web and Client

The document discusses the client-server model that powers the internet. It explains that a client, like a web browser, makes requests to a server which processes the request and returns a response. There are three main models: 1) static HTML pages where the server returns pre-written pages, 2) CGI scripts where the server runs a program to dynamically generate pages based on inputs, and 3) server-side scripting where code embedded in pages is processed by the server to dynamically generate the final HTML sent to the client. The client-server interaction is stateless, with each new request starting a new transaction.

Uploaded by

Abha Bansal
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
73 views

Data Transfer Over The Web and Client

The document discusses the client-server model that powers the internet. It explains that a client, like a web browser, makes requests to a server which processes the request and returns a response. There are three main models: 1) static HTML pages where the server returns pre-written pages, 2) CGI scripts where the server runs a program to dynamically generate pages based on inputs, and 3) server-side scripting where code embedded in pages is processed by the server to dynamically generate the final HTML sent to the client. The client-server interaction is stateless, with each new request starting a new transaction.

Uploaded by

Abha Bansal
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

The Client Server Architecture

The Internet revolves around the client-server architecture. Your computer runs software called the client and it interacts with another software known as the server located at a remote computer. The client is usually a browser such as Internet Explorer, Netscape Navigator or Mozilla. Browsers interact with the server using a set of instructions called protocols. These protocols help in the accurate transfer of data through requests from a browser and responses from the server. There are many protocols available on the Internet. The World Wide Web, which is a part of the Internet, brings all these protocols under one roof. You can, thus, use HTTP, FTP, Telnet, email etc. from one platform - your web browser.

Some common Internet protocols


HTTP (HyperText transfer Protocol): used on the World Wide Web (WWW) for transfering
web pages and files contained in web pages such as images. FTP (File Transfer protocol): employed for transfering files from one machine to the other. SMTP (Simple Mail Transport Protocol): used for email. Telnet Protocol: Used to open telnet sessions. The web employs a connection-less protocol, which means that after every client-server interaction the connection between the two is lost. Let us now examine the client-server inter-communication with three models.

Model #1 of the client-server architecture - Static HTML pages


The client (browser) requests for an HTML file stored on the remote machine through the server software. The server locates this file and passes it to the client. The client then displays this file on your machine. In this case, the HTML page is static. Static pages do not change until the developer modifies them.

Model #2 of the client-server architecture - CGI Scripts


The scenario is slightly different for CGI applications. Here the server has to do more work since CGI programs consume the server machine's processing power. Let us suppose you come across a searchable form on a web page that runs a CGI program. Let us also suppose you type in the word

'computers' as the search query. Your browser sends your request to the server. The server checks the headers and locates the necessary CGI program and passes it the data from the request including your search query "computers". The CGI program processes this data and returns the results to the server. The server then sends this formatted in HTML to your browser which in turn displays the HTML page. Thus the CGI program generates a dynamic HTML page. The contents of the dynamic page depend on the query passed to the CGI program.

Model #3 of the client-server architecture - Server side scripting technologies


The third case also involves dynamic response generated by the use of server side technologies. There are many server side technologies today. Active Server Pages (ASP): A Microsoft technology. ASP pages typically have the extension .asp. Personal Home Pages (PHP): An open source technology. PHP pages typically have .php, .phtml or .php3 file name extensions. Java Server Pages: .jsp pages contain Java code. Server Side Includes (SSI): Involves the embedding of small code snippets inside the HTML page. An SSI page typically has .shtml as its file extension. With these server technologies it has become easier to maintain Web pages especially helpful for a large web site. The developer needs to embed the server-side language code inside the HTML page. This code is passed to the appropriate interpreter which processes these instructions and generates the final HTML displayed by the browser. Note, the embedded server-script code is not visible to the client (even if you check the source of the page) as the server sends ONLY the HTML code. Let's look at PHP as an example. A request sent for a PHP page from a client is passed to the PHP interpreter by the server along with various program variables. The interpreter then processes the PHP code and generates a dynamic HTML output. This is sent to the server which in turn redirects it to the client. The browser is not aware of the functioning of the server. It just receives the HTML code, which it appropriately formats and displays on your computer.

Data transfer over the web and client-server interaction


Data transfer over the Internet starts with an event. The event can be of human origin, for example, you start the browser (a client program) on your computer and request for some information, say an HTML file, located on a remote computer. There are two important ways in which information is requested from a browser, a hyperlink is clicked or a URL is entered in the "Address" or "Location" field.

The event can also be generated from the instructions in a program. Thus, we can automate uploading and downloading of files (data transfer) with the help of a program. Let us suppose you have requested for an HTML document from a remote computer using a web browser. The browser searches for the remote computer and on locating it, passes the request to a program called the server running on this distant computer. The server then checks up your request and tries to locate the HTML file on its hard disk. On finding it, the server sends this file to your computer. If this HTML document has embedded image, video, and/or sound files, the information and the content of such files are also passed to the browser. On receiving data from the server, the client which is a browser in our case, starts to display the HTML page. The client holds the sole prerogative on document display, with no involvement from the servers' side. Once it sends the data to the remote computer, the server, so to say, washes its hands off it. On receipt of all requested data, the client-server connection is lost. Thus, the next time this client asks for some information from the server, the server will treat it as a new request without any recollection of previous requests. This means that client-server interaction is "stateless" with every new request generating a new response.

In addition to the browser, I would like to mention two other clients that you might come across the FTP client and the Telnet client programs. Details on these can be found in separate articles.

You might also like