ECE5650: Network Services. Examples of Network Services

Transcription

1 ECE5650: Network Services Network Services 1 Examples of Network Services Web Instant messaging Remote login P2P file sharing Multi-user network games Streaming stored video clips Internet telephone Real-time video conference Massive parallel computing Network Services 2 1

2 Creating a network app Write programs that run on different end systems and communicate over a network. e.g., Web: Web software communicates with browser software little software written for devices in network core network core devices do not run user application code application on end systems allows for rapid app development, propagation application transport network data link physical application transport network data link physical application transport network data link physical Network Services 3 Goal define services offered by the application layer define the architecture of network applications examine popular application-level protocols: HTTP, FTP, , DNS programming network applications socket API Network Services 4 2

3 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 file sharing 2.7 Socket programming with TCP 2.8 Socket programming with UDP 2.9 Building a Web Goal: define services offered by the application layer define the architecture of network applications programming network applications: socket API Network Services 5 Application architectures Client- (thin vs thick client) Peer-to-peer (P2P) Hybrid of client- and P2P Network Services 6 3

4 Client- architecture Client/Server Client/Client/Server Database Server (e.g. DB2, Oracle) Web Server (e.g. IIS,Apache) Application Server (e.g. WebSphere) : waits to be contacted always-on have permanent IP address farms for scaling clients: initiates communication can be thin (browser-only) or thick (need more than a browser) not always-on may have dynamic IP addresses do not communicate directly with each other Network Services 7 Pure P2P architecture is not always-on arbitrary end systems directly communicate peers are intermittently connected and change IP addresses example: Gnutella Highly scalable But difficult to manage Network Services 8 4

5 Hybrid of client- and P2P Napster File transfer P2P File search centralized: Peers register content at central Peers query same central to locate content Instant messaging Chatting between two users is P2P Presence detection/location centralized: User registers its IP address with central when it comes online User contacts central to find IP addresses of buddies Network Services 9 Processes communicating Process: program running within a host. within same host, two processes communicate using inter-process communication (defined by OS). processes in different hosts communicate by exchanging messages applications with P2P architectures have client processes & processes Network Services 10 5

6 Sockets process sends/receives messages to/from its socket where socket = IP address + port # 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 Socket API available for developers: (1) choice of transport protocol; (2) ability to fix a few parameters. Everything else handled by the OS. Network Services 11 Application layer protocol defines Types of messages exchanged, e.g., request & response messages Syntax of message types: what fields in messages & how fields are delineated Semantics of the fields, i.e., meaning of information in fields Rules for when and how processes send & respond to messages Public-domain protocols: defined in RFCs allows for interoperability e.g., HTTP, SMTP Proprietary protocols: e.g., KaZaA Network Services 12 6

7 What services does an application need? Data loss some apps (e.g., audio) can tolerate some loss other apps (e.g., file transfer, telnet) require 100% reliable data transfer Timing some apps (e.g., Internet telephony, interactive games) require low delay to be effective Bandwidth some apps (e.g., multimedia) require minimum amount of bandwidth to be effective other apps ( elastic apps ) make use of whatever bandwidth they get Network Services 13 Service requirements of common apps Application Data loss Bandwidth Time Sensitive file transfer Web documents real-time audio/video stored audio/video interactive games instant messaging no loss no loss no loss loss-tolerant loss-tolerant loss-tolerant no loss elastic elastic elastic audio: 5kbps-1Mbps video:10kbps-5mbps same as above few kbps up elastic no no no yes, 100 s msec yes, few secs yes, 100 s msec yes and no Network Services 14 7

8 Network Applications Summary Network applications architecture: client/, P2P, hyprid of both Sockets (IP+port): socket API offered by OS and used by processes to communicate Application Layer services: specify syntax and type of msgs, rules of send/receive have data loss, timing and bandwidth Network Services 15 Web and HTTP (hyper-text transfer protocol) Web page consists of objects Object can be HTML file, JPEG image, Java applet, audio file, Web page consists of base HTML-file which includes several referenced objects Each object is addressable by a URL (Uniform Resource Locator) Example URL: protocol host name path name Network Services 16 8

9 HTTP overview HTTP: hypertext transfer protocol Web s application layer protocol Stateless Protocol client/ model client: browser that requests, receives, displays Web objects : Web sends objects in response to requests HTTP 1.0: RFC 1945 HTTP 1.1: RFC 2068 PC running Explorer Mac running Navigator HTTP request HTTP response HTTP request HTTP response Server running Apache Web Network Services 17 HTTP overview (continued) Uses TCP (transport layer protocol): client initiates TCP connection (creates socket) to, port 80 accepts TCP connection from client HTTP messages (applicationlayer protocol messages) exchanged between browser (HTTP client) and Web (HTTP ) TCP connection closed HTTP is stateless maintains no information about past client requests aside Protocols that maintain state are complex! past history (state) must be maintained if /client crashes, their views of state may be inconsistent, must be reconciled Network Services 18 9

10 HTTP connections Nonpersistent HTTP At most one object is sent over a TCP connection. HTTP/1.0 uses nonpersistent HTTP Persistent HTTP Multiple objects can be sent over single TCP connection between client and. HTTP/1.1 uses persistent connections in default mode Connection established when the 1st web page is requested and used for all subsequent pages/objects requests until a web timeout value is reached. Either the client or can close the persistent connection by including the connection-token "close" in the Connectionheader field of the http request/reply. Network Services 19 Nonpersistent HTTP Suppose user enters URL (contains text, references to 10 jpeg images) 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.index 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 time Network Services 20 10

11 Nonpersistent HTTP (cont.) 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. Network Services 21 Response time modeling Definition of RTT (Round Trip Time): time to send a small packet to travel from client to and back. Response time: one RTT to initiate TCP connection (always needed) one RTT for HTTP request and first few bytes of HTTP response to return file transmission time total = 2RTT+transmit time (depends on file size and bandwidth) initiate TCP connection RTT request file RTT file received time time time to transmit file Network Services 22 11

12 Persistent HTTP Nonpersistent HTTP issues: requires 2 RTTs per object OS overhead for each TCP connection browsers often open parallel TCP connections to fetch referenced objects Persistent HTTP leaves connection open after sending response subsequent HTTP messages between same client/ sent over open connection Persistent without pipelining: client issues new request only when previous response has been received one RTT for each referenced object Persistent with pipelining: default in HTTP/1.1 client sends requests as soon as it encounters a referenced object as little as one RTT for all the referenced objects within the requested web page Network Services 23 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 file sharing 2.7 Socket programming with TCP 2.8 Socket programming with UDP 2.9 Building a Web Network Services 24 12

13 HTTP request message two types of HTTP messages: request, response HTTP request message: ASCII (human-readable format) request line (GET, POST, HEAD commands) header lines GET /somedir/page.html HTTP/1.1 Host: User-agent: Mozilla/4.0 Connection: close Accept-language:fr Compare to Connection: Keep-Alive Carriage return, line feed indicates end of message (extra carriage return, line feed) Network Services 25 HTTP request message (RFC 2616): general format Network Services 26 13

14 Uploading form input Post method: Web page often includes form input Input is uploaded to in entity body URL method: Uses GET method Input is uploaded in URL field of request line: Network Services 27 Method types HTTP/1.0 GET POST HEAD asks to leave requested object out of response (used mainly for debugging) HTTP/1.1 GET, POST, HEAD PUT uploads file in entity body to path specified in URL field DELETE deletes file specified in the URL field Network Services 28 14

15 HTTP response message status line (protocol status code and phrase) date at web when file was requested file last modified date 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... Network Services 29 HTTP response status codes In first line in ->client response message. A few sample codes: 200 OK 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 Network Services 30 15

16 Trying out HTTP (client side) for yourself 1. Telnet to your favorite Web : telnet cis.poly.edu 80 Opens TCP connection to port 80 (default HTTP port) at cis.poly.edu. Anything typed in sent to port 80 at cis.poly.edu 2. Type in a GET HTTP request: GET /~ross/ HTTP/1.1 Host: cis.poly.edu By typing this in (hit carriage return twice), you send this minimal (but complete) GET request to HTTP 3. Look at response message sent by HTTP! Network Services 31 User- state: cookies Many major Web sites use cookies: Example: 1) Persistent: file stays on users PC after closing the browser. 2) Non-Persistent (mostly used in J2EE and.net platforms): deleted when user closes browser or logs off the web site. Four components: 1) cookie header line of HTTP response message 2) cookie header line in HTTP request message 3) cookie file kept on user s host, managed by user s browser 4) back-end database at Web site Susan access Internet always from same PC She visits a specific e-commerce site for first time When initial HTTP requests arrives at site, site creates a unique ID and creates an entry in backend database for ID Network Services 32 16

17 Cookies: keeping state (cont.) Cookie file ebay: 8734 client usual http request msg usual http response + Set-cookie: 1678 creates ID 1678 for user entry in backend database Cookie file amazon: 1678 ebay: 8734 one week later: Cookie file amazon: 1678 ebay: 8734 usual http request msg cookie: 1678 usual http response msg usual http request msg cookie: 1678 usual http response msg cookiespecific action cookiespectific action access access Network Services 33 Cookies (continued) What cookies can bring: authorization shopping carts recommendations user session state (Web ) aside Cookies and privacy: cookies permit sites to learn a lot about you you may supply name and to sites search engines use redirection & cookies to learn yet more advertising companies obtain info across sites Network Services 34 17

18 Web caches (proxy ) Goal: satisfy client request without involving origin user sets browser: Web accesses via cache browser sends all HTTP requests to cache object in cache: cache returns object else cache requests object from origin, then returns object to client client client HTTP request HTTP response HTTP request HTTP response Proxy HTTP request HTTP response origin origin Network Services 35 More about Web caching Cache acts as both client and Typically cache is installed by ISP (university, company, residential ISP) Why Web caching? Reduce response time for client request. Reduce traffic and hence cost on an institution s internet access link. Internet dense with caches enables poor content providers to effectively deliver content (but so does P2P file sharing) Network Services 36 18

19 Caching example Assumptions average object size = 100 kbits. Assume 100% usage per user avg. request rate from institution s browsers to origin s = 15/sec delay from internet router to any origin and back to router = 2 sec Consequences institutional network public Internet 1.5 Mbps access link origin s internet router 10 Mbps LAN institutional cache traffic intensity on LAN = LAN utilized bandwidth / LAN bandwidth = (15 requests/sec * 100 kbits) / (10 Mbps) = 15% traffic intensity on access link = access link utilized bandwidth / link bandwidth = (15 requests/sec * 100 kbits) / (1.5 Mbps access) = 100% total delay = Internet delay + access delay + LAN delay = 2 sec + minutes (due to queueing & processing delays) + milliseconds Network Services 37 Caching example (cont) Possible solution increase bandwidth of access link to, say, 10 Mbps Consequences utilization on LAN = 15% utilization on access link = 15% Total delay = Internet delay + access delay + LAN delay = 2 sec + msecs + msecs often a costly upgrade institutional network public Internet 10 Mbps access link 10 Mbps LAN origin s institutional cache Network Services 38 19

20 Caching example (cont) Install cache suppose hit rate is.4 Consequence 40% requests will be satisfied almost immediately 60% requests satisfied by origin utilization of access link reduced to 60%, resulting in negligible delays (queueing delay reduced) total avg delay = Internet delay + access delay + LAN delay = 2 + msecs + msecs institutional network public Internet 1.5 Mbps access link 10 Mbps LAN origin s institutional cache Network Services 39 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> : response contains no object if cached copy is upto-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> object not modified object modified Network Services 40 20

21 HTTP Summary HTTP request msg format and method types: GET, POST, HEAD, PUT, DELATE HTTP response msg format and status codes Cookies and their usage: Persistent vs Non-Persistent cookies Web cache or proxy : Conditional GET (If-modified-since:) in HTTP header Network Services 41 21