ClientServer - <?xml version="1.0"...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" ""> <html xmlns=""> <head> <title>Client/Server Introduction</title> <meta name="copyright" content="Copyright &#169; 2008 by Martin B. Wolske" /> <link rel="stylesheet" type="text/css" media="screen, projection, print" href="" /> <script src="" charset="utf-8" type="text/javascript"></script> <link rel="stylesheet" type="text/css" media="screen, projection, print" href="" /> </head> <body> <div class="background"> <img id="head-icon" alt="graphic with four colored squares" src="" /> </div> <div class="slide cover"> <div style="text- align:center;width:60%;position:relative;left:20%;top:20%"> <h1> The Client/Server Architecture<br /> LIS 451 * Summer 2008<br /> Introduction to Networked Information Systems<br /> </h1> <p> <a href=""> Martin Wolske, Ph.D.</a> ( <a href=""></a>) </p> </div> </div> <div class="slide" id="OpeningDiscussion"> <h1>Opening Discussion</h1> <ul> <li>What is a client?</li> <li>What is a server?</li> <li>How does a client interact with a server?</li> </ul> </div> <div class="slide" id="OpenProtocols"> <h1>Open Protocols</h1> <ul> <li> In order for a client and server to exchange information, there must be a set of rules that will govern the exchange of data between the two. These rules are defined within a protocol. </li> <li> Protocols can either be defined publicly or kept private. For standard open protocols used on the Internet, the RFC process is most typically used to
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
publish these protocols. </li> <li> While RFC initially stood for Request For Comment, and was the process by which comments on proposed new protocols were solicited, today it is the final, formal publication of Internet standard protocols. </li> <li>RFC #’s for Major Client/Server Protocols: <ul> <li>Simple Mail Transport Protocol (SMTP): 821</li> <li>Telnet: 854</li> <li>File Transfer Protocol (FTP): 959</li> <li>Network News Transport Protocol (NNTP): 977</li> <li>Internet Relay Chat (IRC): 1459</li> <li>Post O ce Protocol (POP): 1725</li> <li>Internet Mail Access Protocol (IMAP): 2060</li> <li>HyperText Transport Protocol (HTTP): 2068 (v1.1)</li> </ul> </li> </ul> </div> <div class="slide" id="RFCForSMTP"> <h1>Reviewing the RFC for Delivering Email (RFC821)</h1> <ul class="incremental"> <li> RFC’s typically provide an introduction, a description of the model, and specifications of the protocol. One place to go to ±nd a listing of all RFC’s that have been
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 02/09/2010 for the course GSLIS LIS451 taught by Professor Martinwolske during the Summer '08 term at University of Illinois at Urbana–Champaign.

Page1 / 16

ClientServer - &lt;?xml version=&quot;1.0&quot;...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online