1 / 11

Data Communications and Computer Networks Chapter 2 CS 3830 Lecture 8

Data Communications and Computer Networks Chapter 2 CS 3830 Lecture 8. Omar Meqdadi Department of Computer Science and Software Engineering University of Wisconsin-Platteville. Web caches (proxy server). user sets browser: Web accesses via cache browser sends all HTTP requests to cache

delilah-contreras
Download Presentation

Data Communications and Computer Networks Chapter 2 CS 3830 Lecture 8

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data Communications and Computer NetworksChapter 2CS 3830 Lecture 8 Omar Meqdadi Department of Computer Science and Software Engineering University of Wisconsin-Platteville

  2. Web caches (proxy server) user sets browser: Web accesses via cache browser sends all HTTP requests to cache cache requests object from origin server, then returns object to client object in cache: cache returns object HTTP request HTTP request HTTP response HTTP response HTTP request HTTP response Goal: satisfy client request without involving origin server origin server Proxy server client client origin server 2: Application Layer 2

  3. More about Web caching cache acts as both client and server typically cache is installed by ISP (university, company, residential ISP) Why Web caching? reduce response time for client request reduce traffic on an institution’s access link. Internet dense with caches: enables “poor” content providers to effectively deliver content (but so does P2P file sharing) 2: Application Layer 3

  4. Caching example Assumptions average object size = 100,000 bits avg. request rate from institution’s browsers to origin servers = 15/sec delay from institutional router to any origin server and back to router = 2 sec Consequences utilization on LAN = 15% utilization on access link = 100% total delay = Internet delay + access delay + LAN delay = 2 sec + minutes + milliseconds origin servers public Internet 1.5 Mbps access link institutional network 10 Mbps LAN 2: Application Layer 4

  5. Caching example (cont) possible solution increase bandwidth of access link to, say, 10 Mbps consequence utilization on LAN = 15% utilization on access link = 15% Total delay = Internet delay + access delay + LAN delay = 2 sec + msecs + msecs often a co$tly upgrade!! origin servers public Internet 10 Mbps access link institutional network 10 Mbps LAN 2: Application Layer 5

  6. Caching example (cont) possible solution: install cache suppose hit rate is 0.4 consequence 40% requests will be satisfied almost immediately 60% requests satisfied by origin server utilization of access link reduced to 60%, resulting in negligible delays (say 10 msec) total avg delay = Internet delay + access delay + LAN delay = .6*(2.01)secs + .4*milliseconds < 1.4 secs origin servers public Internet 1.5 Mbps access link institutional network 10 Mbps LAN institutional cache 2: Application Layer 6

  7. Conditional GET Goal: don’t send object if cache has up-to-date cached version cache: specify date of cached copy in HTTP request If-modified-since: <date> server: response contains no object if cached copy is up-to-date: HTTP/1.0 304 Not Modified HTTP response HTTP/1.0 304 Not Modified server cache HTTP request msg If-modified-since: <date> object not modified HTTP request msg If-modified-since: <date> object modified HTTP response HTTP/1.0 200 OK <data> 2: Application Layer 7

  8. Chapter 2: Application layer 2.1 Principles of network applications 2.2 Web and HTTP 2.3 FTP 2.4 Electronic Mail SMTP, POP3, IMAP 2.5 DNS 2.6 P2P applications 2.7 Socket programming with TCP 2.8 Socket programming with UDP 2.9 Building a Web server 2: Application Layer 8

  9. FTP: the file transfer protocol transfer file to/from remote host client/server model client: side that initiates transfer (either to/from remote) server: remote host ftp: RFC 959 FTP user interface FTP client FTP server file transfer user at host remote file system local file system 2: Application Layer 9

  10. FTP: separate control, data connections FTP client contacts FTP server at port 21, TCP is transport protocol client authorized over control connection client browses remote directory by sending commands over control connection. when server receives “file transfer command”, server opens 2ndTCP connection (for file) to client after transferring one file, server closes data connection. TCP control connection port 21 TCP data connection port 20 FTP client FTP server • server opens another TCP data connection to transfer another file. • control connection: “out of band” • FTP server maintains “state”: current directory, earlier authentication 2: Application Layer 10

  11. FTP commands, responses Sample commands: sent as ASCII text over control channel USER username PASS password LISTreturn list of file in current directory RETR filenameretrieves (gets) file STOR filenamestores (puts) file onto remote host Sample return codes status code and phrase (as in HTTP) 331 Username OK, password required 125 data connection already open; transfer starting 425 Can’t open data connection 452 Error writing file 2: Application Layer 11

More Related