Network Application. Topic. Principle of Network Application. Principle of Network Application
|
|
- Leslie Carter
- 5 years ago
- Views:
Transcription
1 Topic Network Application o Principle of Network Application o Web & HTTP o FTP o o DNS o Peer-to-peer 2 Principle of Network Application o Network Applications web instant messaging remote login P2P file sharing multi- network games streaming stored video clips voice over IP real-time video conferencing grid computing Etc. Principle of Network Application o Application Architecture Client- Peer-to-peer (P2P) Hybrid of client- and P2P 3 4
2 Client-Server o Architecture client/ : always-on host permanent IP address farms for scaling clients: communicate with may be intermittently connected may have dynamic IP addresses do not communicate directly with each other Peer-to-peer o Architecture peer-peer Peers no always-on arbitrary end systems directly communicate peers are intermittently connected and change IP addresses example: Gnutella Highly scalable but difficult to manage Hybrid of client- and P2P o Skype voice-over-ip P2P application centralized : finding address of remote party: client-client connection: direct (not through ) o Instant messaging chatting between two s is P2P centralized service: client presence detection/location registers its IP address with central when it comes online contacts central to find IP addresses of buddies 8 Processes communicating Process: program running within a host. o within same host, two processes communicate using inter-process communication (defined by OS). o processes in different hosts communicate by exchanging messages Client process: process that initiates communication Server process: process that waits to be contacted o Note: applications with P2P architectures have client processes & processes
3 9 Addressing Process - Sockets o process sends/receives messages to/from its socket o socket analogous to door sending process shoves message out door sending process relies on transport infrastructure on other side of door which brings message to socket at receiving process host or process socket TCP with buffers, variables controlled by app developer controlled by OS Internet host or process socket TCP with buffers, variables 10 Application layer protocol defines o Types of messages exchanged, e.g., request, response o Message syntax: what fields in messages & how fields are delineated o Message semantics meaning of information in fields o Rules for when and how processes send & respond to messages Public-domain protocols: o defined in RFCs o allows for interoperability o e.g., HTTP, SMTP Proprietary protocols: o e.g., Skype 11 Transport service that application need Data loss o some apps (e.g., audio) can tolerate some loss o other apps (e.g., file transfer, telnet) require 100% reliable data transfer Timing o some apps (e.g., Internet telephony, interactive games) require low delay to be effective Bandwidth o some apps (e.g., multimedia) require minimum amount of bandwidth to be effective o other apps ( elastic apps ) make use of whatever bandwidth they get 12 Application file transfer Web documents real-time audio/video stored audio/video interactive games instant messaging Transport service requirements of applications Data loss no loss no loss no loss loss-tolerant loss-tolerant loss-tolerant no loss Bandwidth elastic elastic elastic audio: 5kbps-1Mbps video:10kbps-5mbps same as above few kbps up elastic Time Sensitive no no no yes, 100 s msec yes, few secs yes, 100 s msec yes and no
4 13 Internet transport protocols services TCP service: o connection-oriented: setup required between client and processes o reliable transport between sending and receiving process o flow control: sender won t overwhelm receiver o congestion control: throttle sender when network overloaded o does not provide: timing, minimum bandwidth guarantees UDP service: o unreliable data transfer between sending and receiving process o does not provide: connection setup, reliability, flow control, congestion control, timing, or bandwidth guarantee 14 Internet applications : application & transport protocols Application remote terminal access Web file transfer streaming multimedia Internet telephony Application layer protocol SMTP [RFC 2821] Telnet [RFC 854] HTTP [RFC 2616] FTP [RFC 959] proprietary (e.g. RealNetworks) proprietary (e.g., Vonage,Dialpad) Underlying transport protocol TCP TCP TCP TCP TCP or UDP typically UDP Web and HTTP Web & HTTP o Web page consists of objects o Object can be HTML file, JPEG image, Java applet, audio file, o Web page consists of base HTML-file which includes several referenced objects o Each object is addressable by a URL o Example URL: 16 host name path name
5 17 HTTP overview HTTP: hypertext transfer protocol o Web s application layer protocol o client/ model client: browser that requests, receives, displays Web objects : Web sends objects in response to requests o HTTP 1.0: RFC 1945 o HTTP 1.1: RFC 2068 PC running Explorer Mac running Navigator Server running Apache Web 18 HTTP overview (continued) Uses TCP: o client initiates TCP connection (creates socket) to, port 80 o accepts TCP connection from client o HTTP messages (application-layer protocol messages) exchanged between browser (HTTP client) and Web (HTTP ) o TCP connection closed HTTP is stateless o maintains no information about past client requests aside Protocols that maintain state are complex! o past history (state) must be maintained o if /client crashes, their views of state may be inconsistent, must be reconciled 19 HTTP connections Nonpersistent HTTP o At most one object is sent over a TCP connection. o HTTP/1.0 uses nonpersistent HTTP Persistent HTTP o Multiple objects can be sent over single TCP connection between client and. o HTTP/1.1 uses persistent connections in default mode 20 Nonpersistent HTTP Suppose enters URL time 1a. HTTP client initiates TCP connection to HTTP (process) at on port HTTP client sends HTTP request message (containing URL) into TCP connection socket. Message indicates that client wants object somedepartment/home.in dex (contains text, references to 10 jpeg images) 1b. HTTP at host waiting for TCP connection at port 80. accepts connection, notifying client 3. HTTP receives request message, forms response message containing requested object, and sends message into its socket
6 Nonpersistent HTTP (cont.) Non-Persistent HTTP: Response time time 5. HTTP client receives response message containing html file, displays html. Parsing html file, finds 10 referenced jpeg objects 6. Steps 1-5 repeated for each of 10 jpeg objects 4. HTTP closes TCP connection. Definition of RTT: time to send a small packet to travel from client to and back. Response time: o one RTT to initiate TCP connection o one RTT for HTTP request and first few bytes of HTTP response to return o file transmission time total = 2RTT+transmit time initiate TCP connection RTT request file RTT file received time time time to transmit file Persistent HTTP Nonpersistent HTTP issues: o requires 2 RTTs per object o OS overhead for each TCP connection o browsers often open parallel TCP connections to fetch referenced objects Persistent HTTP o leaves connection open after sending response o subsequent HTTP messages between same client/ sent over open connection Persistent without pipelining: o client issues new request only when previous response has been received o one RTT for each referenced object Persistent with pipelining: o default in HTTP/1.1 o client sends requests as soon as it encounters a referenced object o as little as one RTT for all the referenced objects 24 HTTP request message o two types of HTTP messages: request, response o HTTP request message: ASCII (human-readable format) request line (GET, POST, HEAD commands) Carriage return, line feed indicates end of message header lines GET /somedir/page.html HTTP/1.1 Host: User-: Mozilla/4.0 Connection: close Accept-language:fr (extra carriage return, line feed)
7 HTTP request message: general format Uploading form input Post method: o Web page often includes form input o Input is uploaded to in entity body URL method: o Uses GET method o Input is uploaded in URL field of request line: HTTP/1.0 o GET o POST o HEAD Method types asks to leave requested object out of response HTTP/1.1 o GET, POST, HEAD o PUT uploads file in entity body to path specified in URL field o DELETE deletes file specified in the URL field HTTP response message status line (protocol status code status phrase) data, e.g., requested HTML file header lines HTTP/ OK Connection close Date: Thu, 06 Aug :00:15 GMT Server: Apache/1.3.0 (Unix) Last-Modified: Mon, 22 Jun Content-Length: 6821 Content-Type: text/html data data data data data
8 OK HTTP response status codes In first line in ->client response message. A few sample codes: 31 request succeeded, requested object later in this message 301 Moved Permanently requested object moved, new location specified later in this message (Location:) 400 Bad Request request message not understood by 404 Not Found requested document not found on this 505 HTTP Version Not Supported client ebay 8734 cookie file ebay 8734 amazon 1678 one week later: ebay 8734 amazon 1678 Cookies: keeping state (cont.) usual http request msg usual http response Set-cookie: 1678 usual http request msg cookie: 1678 usual http response msg usual http request msg cookie: 1678 usual http response msg Amazon creates ID 1678 for create entry cookiespecific action cookiespectific action access access backend database User- state: cookies Many major Web sites use cookies Four components: 1) cookie header line of HTTP response message 2) cookie header line in HTTP request message 3) cookie file kept on s host, managed by s browser 4) back-end database at Web site Cookies (continued) What cookies can bring: o authorization o shopping carts o recommendations o session state (Web ) How to keep state : o protocol endpoints: maintain state at sender/receiver over multiple transactions o cookies: http messages carry state Example: o Susan always access Internet always from PC o visits specific e-commerce site for first time o when initial HTTP requests arrives at site, site creates: unique ID entry in backend database for ID aside Cookies and privacy: o cookies permit sites to learn a lot about you o you may supply name and to sites
9 Web caches (proxy ) Goal: satisfy client request without involving origin o sets browser: Web accesses via cache Proxy o browser sends all HTTP requests to cache client object in cache: cache returns object else cache requests object from origin client, then returns object to client origin origin More about Web caching o cache acts as both client and o typically cache is installed by ISP (university, company, residential ISP) Why Web caching? o reduce response time for client request o reduce traffic on an institution s access link. o Internet dense with caches: enables poor content providers to effectively deliver content (but so does P2P file sharing) Caching example Assumptions o average object size = 100,000 bits o avg. request rate from institution s browsers to origin s = 15/sec o delay from institutional router to any origin and back to router = 2 sec Consequences o utilization on LAN = 15% o utilization on access link = 100% o total delay = Internet delay + access delay + LAN delay = 2 sec + minutes + milliseconds 35 institutional network public Internet 1.5 Mbps access link 10 Mbps LAN origin s institutional cache 36 Caching example (cont) possible solution o increase bandwidth of access link to, say, 10 Mbps consequence o utilization on LAN = 15% o utilization on access link = 15% o Total delay = Internet delay + access delay + LAN delay = 2 sec + msecs + msecs o often a costly upgrade institutional network public Internet 10 Mbps access link 10 Mbps LAN origin s institutional cache
10 Caching example (cont) possible solution: install cache o suppose hit rate is 0.4 consequence o 40% requests will be satisfied almost immediately o 60% requests satisfied by origin o utilization of access link reduced to 60%, resulting in negligible delays (say 10 msec) o total avg delay = Internet delay + access delay + LAN delay =.6*(2.01) secs +.4*milliseconds < 1.4 secs 37 institutional network public Internet 1.5 Mbps access link 10 Mbps LAN origin s institutional cache Conditional GET o Goal: don t send object if cache has up-to-date cached version o cache: specify date of cached copy in HTTP request If-modifiedsince: <date> o : response contains no object if cached copy is up-to-date: HTTP/ Not Modified cache HTTP request msg If-modified-since: <date> HTTP response HTTP/ Not Modified HTTP request msg If-modified-since: <date> HTTP response HTTP/ OK <data> FTP: the file transfer protocol object not modified object modified FTP File Transfer Protocol 40 This image cannot currently be displayed. at host FTP interface FTP client local file system file transfer FTP remote file system o transfer file to/from remote host o client/ model client: side that initiates transfer (either to/from remote) : remote host o ftp: RFC 959 o ftp : port 21
11 41 FTP: separate control, data connections o FTP client contacts FTP at port 21, TCP is transport protocol o client authorized over control connection o client browses remote directory by sending commands over control connection. o when receives file transfer command, opens 2 nd TCP connection (for file) to client o after transferring one file, closes data connection. FTP client TCP control connection port 21 TCP data connection port 20 FTP o opens another TCP data connection to transfer another file. o control connection: out of band o FTP maintains state : current directory, earlier authentication 42 FTP commands, responses Sample commands: o sent as ASCII text over control channel o USER name o PASS password o LIST return list of file in current directory o RETR filename retrieves (gets) file o STOR filename stores (puts) file onto remote host Sample return codes o status code and phrase (as in HTTP) o 331 Username OK, password required o 125 data connection already open; transfer starting o 425 Can t open data connection o 452 Error writing file E - Mail 44 Electronic Mail Three major components: o s o mail s o simple mail transfer protocol: SMTP User Agent o a.k.a. mail reader o composing, editing, reading mail messages o e.g., Eudora, Outlook, elm, Mozilla Thunderbird o outgoing, incoming messages stored on mail SMTP mail SMTP SMTP outgoing message queue mail mailbox
12 45 Electronic Mail: mail s Mail Servers o mailbox contains incoming messages for o message queue of outgoing (to be sent) mail messages o SMTP protocol between mail s to send messages client: sending mail : receiving mail mail SMTP mail SMTP SMTP mail 46 Electronic Mail: SMTP [RFC 2821] o uses TCP to reliably transfer message from client to, port 25 o direct transfer: sending to receiving o three phases of transfer handshaking (greeting) transfer of messages closure o command/response interaction commands: ASCII text response: status code and phrase o messages must be in 7-bit ASCII 47 Scenario: Alice sends message to Bob 1) Alice uses UA to compose message and to bob@someschool.edu 2) Alice s UA sends message to her mail ; message placed in message queue 3) Client side of SMTP opens TCP connection with Bob s mail 1 2 mail 3 4 4) SMTP client sends Alice s message over the TCP connection 5) Bob s mail places the message in Bob s mailbox 6) Bob invokes his to read message mail Sample SMTP interaction S: 220 hamburger.edu C: HELO crepes.fr S: 250 Hello crepes.fr, pleased to meet you C: MAIL FROM: <alice@crepes.fr> S: 250 alice@crepes.fr... Sender ok C: RCPT TO: <bob@hamburger.edu> S: 250 bob@hamburger.edu... Recipient ok C: DATA S: 354 Enter mail, end with "." on a line by itself C: Do you like ketchup? C: How about pickles? C:. S: 250 Message accepted for delivery C: QUIT S: 221 hamburger.edu closing connection
13 SMTP: final words o SMTP uses persistent connections o SMTP requires message (header & body) to be in 7-bit ASCII o SMTP uses CRLF.CRLF to determine end of message Comparison with HTTP: o HTTP: pull o SMTP: push o both have ASCII command/response interaction, status codes o HTTP: each object encapsulated in its own response msg o SMTP: multiple objects sent in multipart msg Mail message format SMTP: protocol for exchanging msgs RFC 822: standard for text message format: o header lines, e.g., To: From: Subject: different from SMTP commands! o body the message, ASCII characters only header body blank line Message format: multimedia extensions o MIME: multimedia mail extension, RFC 2045, 2056 o additional lines in msg header declare MIME content type (Multipurpose Internet Mail Extensions) MIME version method used to encode data multimedia data type, subtype, parameter declaration encoded data From: alice@crepes.fr To: bob@hamburger.edu Subject: Picture of yummy crepe. MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Type: image/jpeg base64 encoded data base64 encoded data Mail access protocols This image cannot currently be displayed. SMTP SMTP access protocol sender s mail receiver s mail o SMTP: delivery/storage to receiver s o Mail access protocol: retrieval from POP: Post Office Protocol [RFC 1939] authorization ( <-->) and download IMAP: Internet Mail Access Protocol [RFC 1730] more features (more complex) manipulation of stored msgs on HTTP: gmail, Hotmail, Yahoo! Mail, etc.
14 53 POP3 protocol authorization phase o client commands: : declare name pass: password o responses +OK -ERR transaction phase, client: o list: list message numbers o retr: retrieve message by number o dele: delete o quit S: +OK POP3 ready C: bob S: +OK C: pass hungry S: +OK successfully logged on C: list S: S: S:. C: retr 1 S: <message 1 contents> S:. C: dele 1 C: retr 2 S: <message 1 contents> S:. C: dele 2 C: quit S: +OK POP3 signing off 54 POP3 (more) and IMAP More about POP3 o Previous example uses download and delete mode. o Bob cannot re-read if he changes client o Download-and-keep : copies of messages on different clients o POP3 is stateless across sessions IMAP o Keep all messages in one place: the o Allows to organize messages in folders o IMAP keeps state across sessions: names of folders and mappings between message IDs and folder name DNS Domain Name System DNS: Domain Name System Domain Name System: o distributed database implemented in hierarchy of many name s o application-layer protocol host, routers, name s to communicate to resolve names (address/name translation) note: core Internet function, implemented as application-layer protocol complexity at network s edge 56
15 57 DNS DNS services o hostname to IP address translation o host aliasing Canonical, alias names o mail aliasing o load distribution replicated Web s: set of IP addresses for one canonical name Why not centralize DNS? o single point of failure o traffic volume o distant centralized database o maintenance doesn t scale! 58 Root DNS Servers com DNS s org DNS s edu DNS s yahoo.com DNS s Distributed, Hierarchical Database amazon.com DNS s pbs.org DNS s poly.edu umass.edu DNS sdns s Client wants IP for 1 st approx: o client queries a root to find com DNS o client queries com DNS to get amazon.com DNS o client queries amazon.com DNS to get IP address for 59 DNS: Root name s o contacted by local name that can not resolve name o root name : contacts authoritative name if name mapping not known gets mapping returns mapping to local name e NASA Mt View, CA f Internet Software C. Palo Alto, CA (and 36 other locations) b USC-ISI Marina del Rey, CA l ICANN Los Angeles, CA a Verisign, Dulles, VA c Cogent, Herndon, VA (also LA) d U Maryland College Park, MD g US DoD Vienna, VA h ARL Aberdeen, MD j Verisign, ( 21 locations) k RIPE London (also 16 other locations) i Autonomica, Stockholm (plus 28 other locations) m WIDE Tokyo (also Seoul, Paris, SF) 13 root name s worldwide 60 TLD and Authoritative Servers o Top-level domain (TLD) s: responsible for com, org, net, edu, etc, and all toplevel country domains uk, fr, ca, jp. Network Solutions maintains s for com TLD Educause for edu TLD o Authoritative DNS s: organization s DNS s, providing authoritative hostname to IP mappings for organization s s (e.g., Web, mail). can be maintained by organization or service provider
16 61 Local Name Server o does not strictly belong to hierarchy o each ISP (residential ISP, company, university) has one. also called default name o when host makes DNS query, query is sent to its local DNS acts as proxy, forwards query into hierarchy DNS name resolution example recursive query: o puts burden of name resolution on contacted name o heavy load? local DNS dns.poly.edu requesting host cis.poly.edu root DNS authoritative DNS dns.cs.umass.edu TLD DNS 62 DNS name resolution example o Host at cis.poly.edu wants IP address for gaia.cs.umass.edu iterated query: o contacted replies with name of to contact o I don t know this name, but ask this local DNS dns.poly.edu requesting host cis.poly.edu root DNS TLD DNS 6 authoritative DNS dns.cs.umass.edu gaia.cs.umass.edu DNS: caching and updating records o once (any) name learns mapping, it caches mapping cache entries timeout (disappear) after some time TLD s typically cached in local name s Thus root name s not often visited o update/notify mechanisms under design by IETF RFC gaia.cs.umass.edu 63 64
17 65 DNS records DNS: distributed db storing resource records (RR) RR format: (name, value, type, ttl) o Type=A name is hostname value is IP address o Type=NS name is domain (e.g. foo.com) value is hostname of authoritative name for this domain o Type=CNAME name is alias name for some canonical (the real) name is really east.backup2.ibm.com value is canonical name o Type=MX value is name of mail associated with name DNS protocol, messages DNS protocol : query and reply messages, both with same message format msg header o identification: 16 bit # for query, reply to query uses same # o flags: query or reply recursion desired recursion available reply is authoritative DNS protocol, messages Name, type fields for a query RRs in response to query records for authoritative s additional helpful info that may be used 68 Inserting records into DNS o example: new startup Network Utopia o register name networkuptopia.com at DNS registrar (e.g., Network Solutions) provide names, IP addresses of authoritative name (primary and secondary) registrar inserts two RRs into com TLD : (networkutopia.com, dns1.networkutopia.com, NS) (dns1.networkutopia.com, , A) o create authoritative Type A record for Type MX record for networkutopia.com
18 Peer-to-peer 70 P2P file sharing Example o Alice runs P2P client application on her notebook computer o intermittently connects to Internet; gets new IP address for each connection o asks for Hey Jude o application displays other peers that have copy of Hey Jude. o Alice chooses one of the peers, Bob. o file is copied from Bob s PC to Alice s notebook: HTTP o while Alice downloads, other s uploading from Alice. o Alice s peer is both a Web client and a transient Web. All peers are s = highly scalable! P2P: centralized directory P2P: problems with centralized directory original Napster design 1) when peer connects, it informs central : IP address content 2) Alice queries for Hey Jude 3) Alice requests file from Bob centralized directory Bob peers o single point of failure o performance bottleneck o copyright infringement: target of lawsuit is obvious file transfer is decentralized, but locating content is highly centralized Alice 71 72
19 73 75 Query flooding: Gnutella o fully distributed no central o public domain protocol o many Gnutella clients implementing protocol overlay network: graph o edge between peer X and Y if there s a TCP connection o all active peers and edges form overlay net o edge: virtual (not physical) link o given peer typically connected with < 10 overlay neighbors Gnutella: Peer joining 1. joining peer Alice must find another peer in Gnutella network: use list of candidate peers 2. Alice sequentially attempts TCP connections with candidate peers until connection setup with Bob 3. Flooding: Alice sends Ping message to Bob; Bob forwards Ping message to his overlay neighbors (who then forward to their neighbors.) peers receiving Ping message respond to Alice with Pong message 4. Alice receives many Pong messages, and can then setup additional TCP connections Gnutella: protocol Query message sent over existing TCP connections peers forward Query message QueryHit sent over reverse path Scalability: limited scope flooding Query QueryHit Hierarchical Overlay o between centralized index, query flooding approaches o each peer is either a group leader or assigned to a group leader. TCP connection between peer and its group leader. TCP connections between some pairs of group leaders. o group leader tracks content in its children File transfer: HTTP Query QueryHit ordinary peer group-leader peer neighoring relationships in overlay network
20 77 Comparing Client-, P2P architectures Question : How much time distribute file initially at one to N other computers? File, size F Server d N u N u 1 d 1 u s u 2 d2 Network (with abundant bandwidth) u s : upload bandwidth u i : client/peer i upload bandwidth d i : client/peer i download bandwidth 78 Client-: file distribution time o sequentially sends N copies: NF/u s time o client i takes F/d i time to download Time to distribute F to N clients using client/ approach F Server d N u N u 1 d 1 u s u 2 d2 Network (with abundant bandwidth) = d cs = max { NF/u s, F/min(d i ) } i increases linearly in N (for large N) P2P: file distribution time o must send one copy: F/u s time o client i takes F/d i time to download o NF bits must be downloaded (aggregate) F Server d N u N u 1 d 1 u s u 2 d2 Network (with abundant bandwidth) o fastest possible upload rate (assuming all nodes sending file chunks to same peer): u s + Σu i i=1,n Minimum Distribution Time Comparing Client-, P2P architectures P2P Client-Server d P2P = max { F/u s, F/min(d i ), NF/(u s + Σu i) } i i=1,n 80 N
21 P2P Case Study: BitTorrent BitTorrent (1) o P2P file distribution tracker: tracks peers participating in torrent obtain list of peers peer trading chunks torrent: group of peers exchanging chunks of a file o file divided into 256KB chunks. o peer joining torrent: has no chunks, but will accumulate them over time registers with tracker to get list of peers, connects to subset of peers ( neighbors ) o while downloading, peer uploads chunks to other peers. o peers may come and go o once peer has entire file, it may (selfishly) leave or (altruistically) remain BitTorrent (2) Pulling Chunks o at any given time, different peers have different subsets of file chunks o periodically, a peer (Alice) asks each neighbor for list of chunks that they have. o Alice issues requests for her missing chunks rarest first Sending Chunks: tit-for-tat o Alice sends chunks to four neighbors currently sending her chunks at the highest rate re-evaluate top 4 every 10 secs o every 30 secs: randomly select another peer, starts sending chunks newly chosen peer may join top 4 84 P2P Case study: Skype o P2P (pc-to-pc, pc-tophone, phone-to-pc) Voice-Over-IP (VoIP) application also IM o proprietary applicationlayer protocol (inferred via reverse engineering) o hierarchical overlay Skype login Skype clients (SC) Supernode (SN)
22 Skype: making a call o User starts Skype o SC registers with SN list of bootstrap SNs o SC logs in (authenticate) Skype login o Call: SC contacts SN will callee ID SN contacts other SNs (unknown protocol, maybe flooding) to find addr of callee; returns addr to SC o SC directly contacts callee, overtcp Question? 85
Chapter 2: Application layer
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
More informationChapter 2 Application Layer
Chapter 2 Application Layer Reference: Computer Networking: A Top Down Approach 4 th edition. Jim Kurose, Keith Ross Addison-Wesley, July 2007. Application Layer 1 Chapter 2: Application layer 2.1 Principles
More informationCSEN 404 Introduction to Networks. Mervat AbuElkheir Mohamed Abdelrazik. ** Slides are attributed to J. F. Kurose
CSEN 404 Introduction to Networks Mervat AbuElkheir Mohamed Abdelrazik ** Slides are attributed to J. F. Kurose HTTP Method Types HTTP/1.0 GET POST HEAD asks server to leave requested object out of response
More informationChapter 2 part B: outline
Chapter 2 part B: outline 2.3 FTP 2.4 electronic, POP3, IMAP 2.5 DNS Application Layer 2-1 FTP: the file transfer protocol at host FTP interface FTP client local file system file transfer FTP remote file
More informationCSC 4900 Computer Networks:
CSC 4900 Computer Networks: Email Professor Henry Carter Fall 2017 Villanova University Department of Computing Sciences Review Last week we talked about design principles, and the application protocols
More informationComputer Networking Introduction
Computer Networking Introduction Halgurd S. Maghdid Software Engineering Department Koya University-Koya, Kurdistan-Iraq Lecture No.5 Chapter 2: outline 2.1 principles of network applications app architectures
More informationApplication Layer: , DNS
Application Layer: E-mail, DNS EECS 3214 Slides courtesy of J.F Kurose and K.W. Ross, All Rights Reserved 22-Jan-18 1-1 Chapter 2: outline 2.1 principles of network applications 2.2 Web and HTTP 2.3 electronic
More informationChapter 2: Application Layer. Chapter 2 Application Layer. Some network apps. Application architectures. Chapter 2: Application layer
Chapter 2 Application Layer Computer Networking: A Top Down Approach, 5 th edition. Jim Kurose, Keith Ross Addison-Wesley, April 2009. Chapter 2: Application Layer Our goals: conceptual, implementation
More informationApplication Layer. Pure P2P architecture. Client-server architecture. Processes communicating. Hybrid of client-server and P2P. Creating a network app
Application Layer e- web instant messaging remote login PP file sharing multi- network games streaming stored video (YouTube) voice over IP real-time video conferencing cloud computing Creating a network
More informationApplication Layer. Pure P2P architecture. Client-server architecture. Processes communicating. Hybrid of client-server and P2P. Creating a network app
Application Layer e- web instant messaging remote login P2P file sharing multi- network games streaming stored video (YouTube) voice over IP real-time video conferencing cloud computing Creating a network
More informationCC451 Computer Networks
CC451 Computer Networks Lecture 4 Application Layer (cont d) Application Layer 1 Chapter 2: Application layer 2.1 Principles of network applications 2.2 Web and HTTP 2.3 FTP 2.4 Electronic Mail SMTP, POP3,
More informationApplication layer. Some network apps. Client-server architecture. Hybrid of client-server and P2P. Pure P2P architecture. Creating a network app
Application layer Some network apps e- web instant messaging remote login P2P file sharing multi- network games streaming stored video (YouTube) voice over IP real-time video conferencing cloud computing
More informationChapter 2 Application Layer
Chapter 2 Application Layer A note on the use of these ppt slides: We re making these slides freely available to all (faculty, students, readers). They re in PowerPoint form so you can add, modify, and
More informationCSEN 503 Introduction to Communication Networks
CSEN 503 Introduction to Communication Networks 1-1 Mervat AbuElkheir Hana Medhat Ayman Dayf ** Slides are attributed to J. F. Kurose Roadmap: Application layer Cookies and User-Server State Web caches
More informationCS4/MSc Computer Networking. Lecture 3: The Application Layer
CS4/MSc Computer Networking Lecture 3: The Application Layer Computer Networking, Copyright University of Edinburgh 2005 Network Applications Examine a popular network application: Web Client-server architecture
More informationReview of Previous Lecture
Review of Previous Lecture Network access and physical media Internet structure and ISPs Delay & loss in packet-switched networks Protocol layers, service models Some slides are in courtesy of J. Kurose
More informationLecture 05: Application Layer (Part 02) Domain Name System. Dr. Anis Koubaa
NET 331 Computer Networks Lecture 05: Application Layer (Part 02) Domain Name System Dr. Anis Koubaa Reformatted slides from textbook Computer Networking a top-down appraoch, Fifth Edition by Kurose and
More informationChapter 2: outline. 2.6 P2P applications 2.7 socket programming with UDP and TCP
Chapter 2: outline 2.1 principles of network applications app architectures app requirements 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
More informationChapter 2 Application Layer
Chapter 2 Application Layer A note on the use of these ppt slides: We re making these slides freely available to all (faculty, students, readers). They re in PowerPoint form so you can add, modify, and
More informationCMSC 332 Computer Networking Web and FTP
CMSC 332 Computer Networking Web and FTP Professor Szajda CMSC 332: Computer Networks Project The first project has been posted on the website. Check the web page for the link! Due 2/2! Enter strings into
More informationLecture 7 Application Layer. Antonio Cianfrani DIET Department Networking Group netlab.uniroma1.it
Lecture 7 Application Layer Antonio Cianfrani DIET Department Networking Group netlab.uniroma1.it Application-layer protocols Application: communicating, distributed processes running in network hosts
More informationWWW: the http protocol
Internet apps: their protocols and transport protocols Application e-mail remote terminal access Web file transfer streaming multimedia remote file Internet telephony Application layer protocol smtp [RFC
More informationFTP. Mail. File Transfer Protocol (FTP) FTP commands, responses. Electronic Mail. TDTS06: Computer Networks
TDTS0: Computer Networks Instructor: Niklas Carlsson Email: niklas.carlsson@liu.se FTP Notes derived from Computer Networking: A Top Down Approach, by Jim Kurose and Keith Ross, Addison-Wesley. The slides
More informationChapter 2 Application Layer
CSF531 Advanced Computer Networks 高等電腦網路 Chapter 2 Application Layer 吳俊興 國立高雄大學資訊工程學系 Chapter 2: Outline 2.1 Principles of network applications 2.2 Web and HTTP 2.3 FTP 2.4 Electronic Mail SMTP, POP3,
More informationChapter 2 Application Layer. Lecture 5 DNS. Computer Networking: A Top Down Approach. 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012
Chapter 2 Application Layer Lecture 5 DNS Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012 Application Layer 2-1 Chapter 2: outline 2.1 principles
More informationChapter 2 Application Layer
Chapter 2 Application Layer A note on the use of these ppt slides: We re making these slides freely available to all (faculty, students, readers). They re in PowerPoint form so you can add, modify, and
More informationWeb, HTTP and Web Caching
Web, HTTP and Web Caching 1 HTTP overview HTTP: hypertext transfer protocol Web s application layer protocol client/ model client: browser that requests, receives, displays Web objects : Web sends objects
More informationChapter 2. Application Layer. 2: Application Layer 1
Chapter 2 Application Layer 2: Application Layer 1 Some network apps e-mail web instant messaging remote login P2P file sharing multi-user network games streaming stored video clips voice over IP real-time
More informationChapter P2P file sharing network applications 2.22 Web and HTTP 2.3 FTP DNS
Chapter 2 Application Layer A note on the use of these ppt slides: We re making these slides freely available to all (faculty, students, readers). They re in PowerPoint form so you can add, modify, and
More informationElectronic Mail. Three Components: SMTP SMTP. SMTP mail server. 1. User Agents. 2. Mail Servers. 3. SMTP protocol
SMTP Electronic Mail Three Components: 1. User Agents a.k.a. mail reader e.g., gmail, Outlook, yahoo 2. Mail Servers mailbox contains incoming messages for user message queue of outgoing (to be sent) mail
More informationChapter 2. Application Layer. Chapter 2: Application Layer. Application layer - Overview. Some network apps. Creating a network appication
Mobile network Chapter 2 The Yanmin Zhu Department of Computer Science and Engineering Global ISP Home network Regional ISP Institutional network CSE Department 1 CSE Department 2 Application layer - Overview
More informationChapter 2: Application layer
Chapter 2: Application layer 2. Principles of network applications app architectures app requirements 2.2 Web and HTTP 2.4 Electronic Mail SMTP, POP3, IMAP 2.5 DNS 2.6 P2P applications 2.7 Socket programming
More informationELEC / COMP 177 Fall Some slides from Kurose and Ross, Computer Networking, 5 th Edition
ELEC / COMP 177 Fall 2013 Some slides from Kurose and Ross, Computer Networking, 5 th Edition Project 1 Python HTTP Server Work day: Next Tuesday (Sept 24 th ) Due Thursday, September 26 th by 11:55pm
More informationInternet applications. 2: Application Layer 1
Internet applications 2: Application Layer 1 Recall Internet architecture Intelligence at end systems e.g., web server software communicates with browser software No need to write software for network-core
More informationFoundations of Telematics
Foundations of Telematics Chapter 2 Application Layer Principles of network applications Important application protocols Using sockets Acknowledgement: These slides have been prepared by J.F. Kurose and
More informationELEC / COMP 177 Fall Some slides from Kurose and Ross, Computer Networking, 5 th Edition
ELEC / COMP 177 Fall 2012 Some slides from Kurose and Ross, Computer Networking, 5 th Edition Homework #1 Assigned today Due in one week Application layer: DNS, HTTP, protocols Recommend you start early
More informationCSC 401 Data and Computer Communications Networks
CSC 401 Data and Computer Communications Networks Application Layer: Cookies, Web Caching, SMTP Sec 2.2.4-2.4 Prof. Lina Battestilli Fall 2017 Outline Application Layer (ch 2) 2.1 principles of network
More information1-1. Switching Networks (Fall 2010) EE 586 Communication and. September Lecture 10
EE 586 Communication and Switching Networks (Fall 2010) Lecture 10 September 17 2010 1-1 Announcement Send me your group and get group ID HW3 (short) out on Monday Personal leave for next two weeks No
More informationDomain Name Service. DNS Overview. October 2009 Computer Networking 1
Domain Name Service DNS Overview October 2009 Computer Networking 1 Why DNS? Addresses are used to locate objects (contain routing information) Names are easier to remember and use than numbers DNS provides
More informationEECS 3214: Computer Network Protocols and Applications
EECS 3214: Computer Network Protocols and Applications Suprakash Datta Course page: http://www.eecs.yorku.ca/course/3214 Office: LAS 3043 Email: datta [at] cse.yorku.ca These slides are adapted from Jim
More informationHyperText Transfer Protocol
Outline Introduce Socket Programming Domain Name Service (DNS) Standard Application-level Protocols email (SMTP) HTTP HyperText Transfer Protocol Defintitions A web page consists of a base HTML-file which
More informationLecture 04: Application Layer (Part 01) Principles and the World Wide Web (HTTP) Dr. Anis Koubaa
NET 331 Computer Networks Lecture 04: Application Layer (Part 01) Principles and the World Wide Web (HTTP) Dr. Anis Koubaa Reformatted slides from textbook Computer Networking a top-down appraoch, Fifth
More informationApplication Layer. Goals: Service models. Conceptual aspects of network application protocols Client server paradigm
Application Layer Goals: Conceptual aspects of network application protocols Client server paradigm Service models Review protocols by examining popular application-level protocols HTTP DNS 1 Applications
More informationNetworking. Layered Model. DoD Model. Application Layer. ISO/OSI Model
Networking Networking is concerned with the physical topology of two or more communicating entities and the logical topology of data transmission. Layered Model Systems communicate over a shared communication
More informationChapter 2: outline. 2.6 P2P applications 2.7 socket programming with UDP and TCP
Chapter 2: outline 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 UDP and TCP Application
More informationApplications & Application-Layer Protocols: (SMTP) and DNS
CS 312 Internet Concepts Applications & Application-Layer Protocols: E (SMTP) and DNS Dr. Michele Weigle Department of Computer Science Old Dominion University mweigle@cs.odu.edu http://www.cs.odu.edu/~mweigle/cs312-f11
More informationEECS 3214: Computer Network Protocols and Applications
EECS 3214: Computer Network Protocols and Applications Suprakash Datta datta@cse.yorku.ca Office: LAS 3043 Phone: 416-736-2100 ext 77875 Course page: http://www.cse.yorku.ca/course/3214 These slides are
More informationSection 2: Application layer
Section 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 UDP 2.8 Socket
More informationDomain Name System (DNS) 김현철 ( 화 ) 정보통신융합서울대학교컴퓨터공학부
Domain Name System (DNS) 김현철 2010.09.29 ( 화 ) 정보통신융합서울대학교컴퓨터공학부 Chapter 2 Application Layer A note on the use of these ppt slides: We re making these slides freely available to all (faculty, students,
More informationChapter 2 Application Layer
Chapter 2 Application Layer Computer Networking: A Top Down Approach, 4 th edition. Jim Kurose, Keith Ross Addison-Wesley, July 2007. 2: Application Layer 1 Chapter 2: Application layer 2.1 Principles
More informationChapter II: Application Layer
Chapter II: Application Layer UG3 Computer Communications & Networks (COMN) MAHESH MARINA mahesh@ed.ac.uk Slides thanks to Myungjin Lee, and copyright of Kurose and Ross First, a review Web and HTTP web
More informationLayered Model. DoD Model. ISO/OSI Model
Data Communications vs Networking (later) Communication is concerned with the transmission of data over a communication medium/channel between two entities. Here we are more concerned about EE issues such
More informationChapter 2: Application Layer
Chapter 2: Application Layer Course on Computer Communication and Networks, CTH/GU The slides are adaptation of the slides made available by the authors of the course s main textbook: Computer Networking:
More informationApplication Layer. Goals:
Application Layer Goals: Conceptual aspects of network application protocols Client server paradigm Service models Learn about protocols by examining popular applicationlevel protocols HTTP DNS SMTP, POP3,
More informationApplication Layer. Applications and application-layer protocols. Goals:
Application Layer Goals: Conceptual aspects of network application protocols Client server paradigm Service models Learn about protocols by examining popular applicationlevel protocols HTTP DNS SMTP, POP3,
More informationComputer Networks. Wenzhong Li. Nanjing University
Computer Networks Wenzhong Li Nanjing University 1 Chapter 8. Internet Applications Internet Applications Overview Domain Name Service (DNS) Electronic Mail File Transfer Protocol (FTP) WWW and HTTP Content
More informationApplication Layer Chapter 2
Application Layer Chapter 2 Silvia Giordano SUPSI CH-6928 Manno silvia.giordano@supsi.ch http://www.supsi.ch SUPSI-DTI Silvia Giordano 10/06/2004 Application Layer 1 Chapter goals: learn about protocols
More informationChapter 1 Introduction
Chapter 1 Introduction Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012 Slides adopted from original ones provided by the textbook authors. Introduction
More informationChapter 2 Application Layer
Chapter 2 Application Layer A note on the use of these ppt slides: We re making these slides freely available to all (faculty, students, readers). They re in PowerPoint form so you see the animations;
More informationLecture 6 Application Layer. Antonio Cianfrani DIET Department Networking Group netlab.uniroma1.it
Lecture 6 Application Layer Antonio Cianfrani DIET Department Networking Group netlab.uniroma1.it Application-layer protocols Application: communicating, distributed processes running in network hosts
More informationChapter 2 Application Layer
Chapter 2 Application Layer Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012 Application Layer 2-1 Some network apps e-mail web text messaging remote
More informationCMPE 150/L : Introduction to Computer Networks. Chen Qian Computer Engineering UCSC Baskin Engineering Lecture 5
CMPE 150/L : Introduction to Computer Networks Chen Qian Computer Engineering UCSC Baskin Engineering Lecture 5 1 Any problem of your lab? Due by next Monday (Jan 29) Using Canvas? Email me cqian12@ucsc.edu
More informationApplication Layer. Applications and application-layer protocols. Goals:
Application Layer Goals: Conceptual aspects of network application protocols Client paradigm Service models Learn about protocols by examining popular application-level protocols HTTP DNS 1 Applications
More informationApplication Layer: HTTP
Application Layer: HTTP EECS 3214 Slides courtesy of J.F Kurose and K.W. Ross, All Rights Reserved 23-Jan-18 1-1 Chapter 2: outline 2.1 principles of network applications 2.2 Web and HTTP 2.3 electronic
More informationLecture 6: Application Layer Web proxies, , and SMTP
Lecture 6: Application Layer Web proxies, Email, and SMTP COMP 332, Spring 2018 Victoria Manfredi Acknowledgements: materials adapted from Computer Networking: A Top Down Approach 7 th edition: 1996-2016,
More informationCourse on Computer Communication and
Chapter 2: Application Layer Course on Computer Communication and Networks, CTH/GU The slides are adaptation ti of the slides made available by the authors of the course s main textbook: Computer Networking:
More informationCSCE 463/612 Networks and Distributed Processing Spring 2018
CSCE 463/612 Networks and Distributed Processing Spring 2018 Application Layer II Dmitri Loguinov Texas A&M University February 6, 2018 Original slides copyright 1996-2004 J.F Kurose and K.W. Ross 1 Chapter
More informationCMSC 332 Computer Networks P2P and Sockets
CMSC 332 Computer Networks P2P and Sockets Professor Szajda Announcements Programming Assignment 1 is due Thursday Where are we? What sorts of problems are we having? 2 Recap SMTP is the language that
More informationCSC358 Week 2. Adapted from slides by J.F. Kurose and K. W. Ross. All material copyright J.F Kurose and K.W. Ross, All Rights Reserved
CSC358 Week 2 Adapted from slides by J.F. Kurose and K. W. Ross. All material copyright 1996-2016 J.F Kurose and K.W. Ross, All Rights Reserved Logistics Tutorial this Friday Assignment 1 will be out shortly
More informationInternet Protocol Stack! Principles of Network Applications! Some Network Apps" (and Their Protocols)! Application-Layer Protocols! Our goals:!
Internet Protocol Stack! Principles of Network Applications! application: supporting network applications!! HTTP,, FTP, etc.! transport: endhost-endhost data transfer!! TCP, UDP! network: routing of datagrams
More informationWeb caches (proxy server)
Web caches (proxy server) goal: satisfy client request without involving origin server user sets browser: Web accesses via cache browser sends all HTTP requests to cache object in cache: cache returns
More informationGoal and A sample Network App
Application Layer Goal and A sample Network App Write programs that run on different end systems and communicate over a network. e.g., Web: Web server software communicates with browser software Little
More informationApplications Layer Protocols. Hui Chen, Ph.D. Dept. of Engineering & Computer Science Virginia State University Petersburg, VA 23806
Applications Layer Protocols Hui Chen, Ph.D. Dept. of Engineering & Computer Science Virginia State University Petersburg, VA 23806 1 Acknowledgements Some pictures used in this presentation were obtained
More informationChapter 2: application layer
Chapter 2: outline 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 Application Layer 2-1 Chapter 2: application layer our
More informationChapter 2 Application Layer
Chapter 2 Application Layer These slides are adapted from the original slides provided by J.Kurose and K.W Ross. All material copyright 1996-2012 J.F Kurose and K.W. Ross, All Rights Reserved Computer
More informationChapter 2 Application Layer
Chapter 2 Application Layer A note on the use of these ppt slides: We re making these slides freely available to all (faculty, students, readers). They re in PowerPoint form so you see the animations;
More informationCSC358 Week 3. Adapted from slides by J.F. Kurose and K. W. Ross. All material copyright J.F Kurose and K.W. Ross, All Rights Reserved
CSC358 Week 3 Adapted from slides by J.F. Kurose and K. W. Ross. All material copyright 1996-2016 J.F Kurose and K.W. Ross, All Rights Reserved Logistics Assignment 1 Tutorial 2 is programming exercise,
More informationIntroduction to Computer Networking. Guy Leduc. Chapter 2 Application Layer. Chapter 2: outline
Introduction to Computer Networking Guy Leduc Chapter 2 Application Layer Computer Networking: A Top Down Approach, 6 th edition. Jim Kurose, Keith Ross Addison-Wesley, March 2012 2: Application Layer
More informationNetwork Applications Principles of Network Applications
Network Applications Principles of Network Applications A Network application is an application running on one host and provides communication to another application running on a different host. At the
More informationInternet and Intranet Protocols and Applications
Internet and Intranet Protocols and Applications Lecture 4: General Characteristics of Internet Protocols; the Email Protocol February 10, 2004 Arthur Goldberg Computer Science Department New York University
More informationChapter 2 Application Layer
Chapter 2 Application Layer Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012 All material copyright 1996-2012 J.F Kurose and K.W. Ross, All Rights
More informationComputer Networks and Applications
COMP 3331/COMP 9331 Week 2 Introduction(Protocol Layering) & Application Layer (Principles, Web, E- mail) Reading Guide: Chapter 1, Sections 1.5 Chapter 2, Sections 2.1-2.4 Week2: Introduction & Application
More informationChapter 2 Application Layer. Lecture 4: principles of network applications. Computer Networking: A Top Down Approach
Chapter 2 Application Layer Lecture 4: principles of network applications Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012 Application Layer 2-1 Chapter
More informationApplication Layer Protocols
SC250 Computer Networking I Application Layer Protocols Prof. Matthias Grossglauser School of Computer and Communication Sciences EPFL http://lcawww.epfl.ch 1 Today's Objectives Conceptual, implementation
More informationIntroduction to Computer Networking. Gang Wang Fall 2016
Introduction to Computer Networking Gang Wang Fall 2016 Data Networks A set of interconnected nodes exchange information Sharing of the transmission circuits= "switching". Links allow more than one path
More informationIntroduction to the Application Layer. Computer Networks Term B14
Introduction to the Application Layer Computer Networks Term B14 Intro to Application Layer Outline Current Application Layer Protocols Creating an Application Application Architectures Client-Server P2P
More informationApplications & Application-Layer Protocols: FTP and (SMTP & POP)
COMP 431 Internet Services & Protocols Applications & Application-Layer Protocols: FTP and E ( & POP) Jasleen Kaur February 7, 2019 Application-Layer Protocols Outline Example client/ systems and their
More informationLecture 7: Application Layer Domain Name System
Lecture 7: Application Layer Domain Name System COMP 332, Spring 2018 Victoria Manfredi Acknowledgements: materials adapted from Computer Networking: A Top Down Approach 7 th edition: 1996-2016, J.F Kurose
More informationApplication Layer Protocols
Application Layer Protocols Dr. Ihsan Ullah Department of Computer Science & IT University of Balochistan, Quetta Pakistan Email: ihsan.ullah.cs@gmail.com These slides are adapted from the slides accompanying
More informationReview for Internet Introduction
Review for Internet Introduction What s the Internet: Two Views View 1: Nuts and Bolts View billions of connected hosts routers and switches protocols control sending, receiving of messages network of
More informationLecture 2 - Application Layer. Lecture 1 Review. Application Layer. Principles of network applications. Notes. Notes. Notes. Notes
Lecture 2 - Application Layer Networks and Security Jacob Aae Mikkelsen IMADA September 9, 2013 September 9, 2013 1 / 101 Lecture 1 Review Explain in short the following terms Protocol Network Edge Network
More informationThe Application Layer: SMTP, FTP
The Application Layer: SMTP, FTP CS 352, Lecture 5 http://www.cs.rutgers.edu/~sn624/352-s19 Srinivas Narayana 1 Recap: Application-layer protocols DNS: lookup a (machine-readable) address using a (humanreadable)
More informationChapter 2 Application Layer
Chapter 2 Application Layer Chapter 2: outline 2.1 principles of network applications 2.2 Web and HTTP 2.3 electronic mail SMTP, POP3, IMAP 2.4 DNS 2.5 P2P applications 2.6 video streaming and content
More informationCMPE 150/L : Introduction to Computer Networks. Chen Qian Computer Engineering UCSC Baskin Engineering Lecture 4
CMPE 150/L : Introduction to Computer Networks Chen Qian Computer Engineering UCSC Baskin Engineering Lecture 4 1 Lab schedule confirmation Mondays, 12:00-2:00pm Tuesdays, 11:00am-1:00pm Wednesdays, 4:00-6:00pm
More informationChapter 2: Application layer
Chapter 2 Application Layer A note on the use of these ppt slides: Were making these slides freely available to all (faculty, students, readers). Theyre in PowerPoint form so you can add, modify, and delete
More informationCSC 401 Data and Computer Communications Networks
CSC 401 Data and Computer Communications Networks Application Layer DNS and P2P Sec 2.4 2.5 Prof. Lina Battestilli Fall 2017 Outline Application Layer (ch 2) 2.1 principles of network applications 2.2
More informationCSCD 330 Network Programming Winter 2015
CSCD 330 Network Programming Winter 2015 Lecture 5 Application Layer Reading: Chapter 2 Still Some Material in these slides from J.F Kurose and K.W. Ross All material copyright 1996-2007 1 More Network
More informationCS 3516: Advanced Computer Networks
Welcome to CS 3516: Adanced Computer Networks Prof. Yanhua Li Time: 9:00am 9:50am M, T, R, and F Location: Fuller 320 Fall 2017 A-term 1 Some slides are originally from the course materials of the textbook
More informationCMSC 322 Computer Networks Applications and End-To- End
CMSC 322 Computer Networks Applications and End-To- End Professor Doug Szajda CMSC 332: Computer Networks Announcements Project 2 has been posted and is due Monday, February 8 (No extension!) Homework
More informationCreating a network app
Chapter 2: Application Layer Chapter 2 Application Layer Our goals: conceptual, implementation aspects of network application protocols transport-layer service models client- paradigm peer-to-peer paradigm
More information