Introduction to Berkeley Sockets

Similar documents
Introduction to Berkeley Sockets

Introduction to Berkeley Sockets

Network Programming in C: The Berkeley Sockets API. Networked Systems 3 Laboratory Sessions

ECE 435 Network Engineering Lecture 2

Network Programming in C. Networked Systems 3 Laboratory Sessions and Problem Sets

The Berkeley Sockets API. Networked Systems Architecture 3 Lecture 4

Hyo-bong Son Computer Systems Laboratory Sungkyunkwan University

Tutorial on Socket Programming

ECE 435 Network Engineering Lecture 2

CS321: Computer Networks Socket Programming

Group-A Assignment No. 6

Socket Programming. CSIS0234A Computer and Communication Networks. Socket Programming in C

CS321: Computer Networks Introduction to Application Layer

CS 640: Computer Networking

CS118 Discussion 1B, Week 1. Taqi Raza BUNCHE 1209B, Fridays 12:00pm to 1:50pm

Lecture 24. Thursday, November 19 CS 375 UNIX System Programming - Lecture 24 1

Socket Programming for TCP and UDP

UNIX Network Programming. Overview of Socket API Network Programming Basics

CLIENT-SIDE PROGRAMMING

Types (Protocols) Associated functions Styles We will look at using sockets in C Java sockets are conceptually quite similar

COMP/ELEC 429/556 Introduction to Computer Networks

CSC209H Lecture 9. Dan Zingaro. March 11, 2015

Christian Tschudin (basierend auf einem Foliensatz von C. Jelger und T. Meyer) Departement Mathematik und Informatik, Universität Basel

The BSD UNIX Socket Interface (CS 640 Lecture) Assignment 1. Interprocess Communication (IPC) Work Individually (no groups)

A Client-Server Exchange

Unix Network Programming

TCP: Three-way handshake

Socket Programming TCP UDP

Network programming(i) Lenuta Alboaie

Oral. Total. Dated Sign (2) (5) (3) (2)

Hybrid of client-server and P2P. Pure P2P Architecture. App-layer Protocols. Communicating Processes. Transport Service Requirements

Network Programming Worksheet 2. Simple TCP Clients and Servers on *nix with C.

Ports under 1024 are often considered special, and usually require special OS privileges to use.

CS 3516: Computer Networks

Sockets. Dong-kun Shin Embedded Software Laboratory Sungkyunkwan University Embedded Software Lab.

Sockets. Jin-Soo Kim Computer Systems Laboratory Sungkyunkwan University

CS 43: Computer Networks. 05: Socket Programming September 12-14, 2018

Lecture 7. Followup. Review. Communication Interface. Socket Communication. Client-Server Model. Socket Programming January 28, 2005

WinSock. What Is Sockets What Is Windows Sockets What Are Its Benefits Architecture of Windows Sockets Network Application Mechanics

Context. Distributed Systems: Sockets Programming. Alberto Bosio, Associate Professor UM Microelectronic Departement

SOCKET PROGRAMMING. What is a socket? Using sockets Types (Protocols) Associated functions Styles

Elementary TCP Sockets

A Socket Example. Haris Andrianakis & Angelos Stavrou George Mason University

Application Programming Interfaces

CSC209H Lecture 10. Dan Zingaro. March 18, 2015

Network Programming November 3, 2008

Network Software Implementations

PA #2 Reviews. set_name, get_name, del_name. Questions? Will be modified after PA #4 ~

How do we Communicate? Introduction to Unix Network Programming. What does Alice do? What does Bob do? Two simplest networking programs

Department of Computer Science

Introduction to Socket Programming

Socket Programming. Dr. -Ing. Abdalkarim Awad. Informatik 7 Rechnernetze und Kommunikationssysteme

What s an API? Do we need standardization?

Review. Preview. Closing a TCP Connection. Closing a TCP Connection. Port Numbers 11/27/2017. Packet Exchange for TCP Connection

Network Socket Programming - 3 BUPT/QMUL

Programming with TCP/IP. Ram Dantu

CSE 124 Discussion Section Sockets Programming 10/10/17

CSE 333 SECTION 8. Sockets, Network Programming

Network Socket Programming - 3 BUPT/QMUL

Topics for this Week

Outline. Operating Systems. Socket Basics An end-point for a IP network connection. Ports. Network Communication. Sockets and the OS

EECS122 Communications Networks Socket Programming. Jörn Altmann

Unix Network Programming Chapter 4. Elementary TCP Sockets 광운대학교컴퓨터과학과 정보통신연구실 석사과정안중현

TCP/IP Sockets in C: Practical Guide for Programmers. Computer Chat. Internet Protocol (IP) IP Address. Transport Protocols. Ports

Socket Programming. #In the name of Allah. Computer Engineering Department Sharif University of Technology CE443- Computer Networks

CSE 333 Lecture 16 - network programming intro

CS307 Operating Systems Processes

Processes. Process Concept. The Process. The Process (Cont.) Process Control Block (PCB) Process State

Piotr Mielecki Ph. D.

ICT 6544 Distributed Systems Lecture 5

Message passing systems are popular because they support client-server interactions, where: clients send messages to servers requesting a server.

Socket Programming. Sungkyunkwan University. Hyunseung Choo Copyright Networking Laboratory

Outline. Distributed Computer Systems. Socket Basics An end-point for a IP network connection. Ports. Sockets and the OS. Transport Layer.

CSMC 412. Computer Networks Prof. Ashok K Agrawala Ashok Agrawala Set 2. September 15 CMSC417 Set 2 1

Programming Internet with Socket API. Hui Chen, Ph.D. Dept. of Engineering & Computer Science Virginia State University Petersburg, VA 23806

Lecture 3 Overview! Last Lecture! TCP/UDP and Sockets introduction!

Lab 0. Yvan Petillot. Networks - Lab 0 1

NETWORK PROGRAMMING. Instructor: Junaid Tariq, Lecturer, Department of Computer Science

Announcements. CS 5565 Network Architecture and Protocols. Queuing. Demultiplexing. Demultiplexing Issues (1) Demultiplexing Issues (2)

Networked Applications: Sockets. End System: Computer on the Net

The User Datagram Protocol

Computer Networks Prof. Ashok K. Agrawala

1 /* client.c - adapted from code for example client program that uses TCP */ 2 /*Modified by Vincent Chu, Winter

Outline. Distributed Computing Systems. Socket Basics (1 of 2) Socket Basics (2 of 2) 3/28/2014

Session NM056. Programming TCP/IP with Sockets. Geoff Bryant Process software

UNIX System Programming Lecture 19: IP Sockets

Communication. Sockets (Haviland Ch. 10)

// socket for establishing connections

CSE 333 SECTION 7. Client-Side Network Programming

TCP Network Programming in C

sottotitolo Socket Programming Milano, XX mese 20XX A.A. 2016/17 Federico Reghenzani

System Programming. Sockets

Socket Programming 2007/03/28

IPv6 Porting Applications

Sockets 15H2. Inshik Song

Processes communicating. Network Communication. Sockets. Addressing processes 4/15/2013

Socket Programming. What is a socket? Using sockets. Types (Protocols) Associated functions Styles

UNIX Sockets. Developed for the Azera Group By: Joseph D. Fournier B.Sc.E.E., M.Sc.E.E.

CSE 333 SECTION 7. C++ Virtual Functions and Client-Side Network Programming

Chapter 6. The Transport Layer. Transport Layer 3-1

Transcription:

INF1060: Introduction to Operating Systems and Data Communication Data Communication: Introduction to Berkeley Sockets Michael Welzl (revised by Hans Petter Taugbøl Kragset 2015) (adapted from lectures by Pål Halvorsen, Carsten Griwodz & Olav Lysne)

Big Picture Machine 1 Machine 2 process A process B network

Goal Introduce socket API We will write two programs A client and a server Each will run on one machine the server will run on vor.ifi.uio.no (129.240.65.59) They will work as follows The client sends the text Hello world! to the server The server writes the received text on the screen The server sends the received text back to the client and quits The client writes the received text onto the screen and quits

What we want Machine 1 client vor.ifi.uio.no server Hello world! Hello world! network Hello world! Hello world!

What we want Client <necessary includes> int main() { char buf[13]; <Declare some more data structures> <Create a socket called sd > <Identify the server that you want to contact> <Connect to the server> /* Send data */ write(sd, Hello world!, 12); /* Read data from the socket */ read(sd, buf, 12); /* Add a string termination sign, and write to the screen. */ buf[12] = \0 ; printf( %s\n, buf); Server <necessary includes> int main() { char buf[13]; <declare some more data structures> <create a socket called request-sd > <Define how the client can connect> <Wait for a connection, and create a new socket sd for that connection> <Identify the server that you want to contact> /* read data from the sd and write it to the screen */ read(sd, buf, 12); buf[12] = \0 ; printf( %s\n, buf ); /* send data back over the connection */ write(sd, buf, 12); } <Closing code> } <Closing code>

Read & Write Same functions used for files etc. The call read(sd, buffer, n); Reads up to n characters From socket sd Stores them in the character array buffer The call write(sd, buffer, n); Writes up to n characters From character array buffer To the socket sd

Alternatives to Read & Write The call recv(sd, buffer, n, flags); Reads up to n characters From socket sd Stores them in the character array buffer Flags, normally just 0, but e.g., MSG_DONTWAIT, MSG_MORE, The call send(sd, buffer, n, flags); Writes up to n characters From character array buffer To the socket sd Flags Several similar functions like to/from, msg

Creation of a connection One side must be the active one take the initiative in creating the connection this side is called the client The other side must be passive it is prepared for accepting connections waits for someone else to take initiative for creating a connection this side is called the server This use of the words client and server is not entirely consistent with everyday use, but for programming this is conventional From now: server is a process, not a machine

Special for the server side In case of TCP one socket on the server side is dedicated to waiting for a connection for each client that takes the initiative, a separate socket on the server side is created this is useful for all servers that must be able to serve several clients concurrently (web servers, mail servers, )

To do slightly more details Client <Necessary includes> int main() { char buf[13]; <Declare some more data structures> <Create a socket called sd > <Identify the server that you want to contact> <Connect to the server> /* Send data */ write(sd, Hello world!, 12); /* Read data from the socket */ read(sd, buf, 12); /* Add a string termination sign, and write to the screen. */ buf[12] = \0 ; printf( %s\n, buf); Server <Necessary includes> int main() { char buf[13]; <Declare some more data structures> <Create a socket called request-sd > <Define how the client can connect> <Wait for a connection, and create a new socket sd for that connection> /* read data from the sd and write it to the screen */ read(sd, buf, 12); buf[12] = \0 ; printf( %s\n, buf ); /* send data back over the connection */ write(sd, buf, 12); } <Closing code> } <Closing code>

<Necessary includes> #include <netinet/in.h> #include <sys/socket.h> #include <netdb.h> #include <stdio.h> #include <string.h> Ø prototypes & defines (htons, etc.) Ø sockaddr_in Ø prototypes (send, connect, etc.) Ø defines Ø prototypes (gethostbyame, etc.) Ø prototypes (printf, etc.) Ø prototypes (memset, etc.) These five files are needed by both client and server They include definitions and declarations as described on the following sides Some systems will have the same declarations in different files the above examples should work at IFI (see /usr/include on Linux & Solaris) man-pages will have the info you need

<Create a socket> Client /* declarations */ int sd; /* creation of the socket */ sd = socket(pf_inet, SOCK_STREAM, IPPROTO_TCP); Server /* declarations */ int request_sd; /* creation of the socket */ request_sd = socket(pf_inet, SOCK_STREAM, IPPROTO_TCP); Call to the function socket() creates a transport control block (hidden in kernel), and returns a reference to it (integer used as index) user kernel sd control block control block control block

More about the socket call sd = socket(int domain, int type, int protocol) PF_INET, SOCK_STREAM and IPPROTO_TCP are constants that are defined in the included files The use of the constants that we used on the previous slides (and above) creates a TCP socket Many other possibilities exist Domain: PF_UNIX, PF_INET, PF_INET6, Type: SOCK_STREAM, SOCK_DGRAM, Protocol: IPPROTO_TCP, IPPROTO_UDP, protocol can be NULL, OS choses apropriate proocol (use with care!)

How to identify clients to accept, and servers to contact? Machine?? by its IP address (e.g., 129.240.65.59) Application/service/program?? by (IP address and) port number standard applications have own, well-known port numbers SSH: 22 Mail: 25 Web: 80 Look in /etc/services for more

Address structure struct sockaddr_in : sin_family sin_port sin_addr sin_zero address family used (defined through a macro) 16-bit transport protocol port number 32-bit IP address defined as a new structure in_addr having one s_addr element only padding (to have an equal size as sockaddr) declared in <netinet/in.h> Defines IP address and port number in a way the Berkeley socket API needs it man 7 ip

Address structure Client Server /* declaration */ struct sockaddr_in serveraddr; /* declaration */ struct sockaddr_in serveraddr; /* clear the structure */ memset(&serveraddr, 0, sizeof(struct sockaddr_in)); /* This will be an address of the * Internet family */ serveraddr.sin_family = AF_INET; /* Add the server address vor */ inet_pton(af_inet, 129.240.65.59, &serveraddr.sin_addr); /* Add the port number */ serveraddr.sin_port = htons(2009); /* clear the structure */ memset(&serveraddr, 0, sizeof(struct sockaddr_in)); /* This will be an address of the * Internet family */ serveraddr.sin_family = AF_INET; /* Allow all own addresses to receive */ serveraddr.sin_addr.s_addr = INADDR_ANY; /* Add the port number */ serveraddr.sin_port = htons(2009);

Address structure Fill address type ( family ), address and port number into the structure serveraddr.sin_family = AF_INET; serveraddr.sin_addr.s_addr = INADDR_ANY; inet_pton( AF_INET, 129.240.65.59, &serveraddr.sin_addr ); (@ server) (@ client) serveraddr.sin_port = htons( 2009 ); AF_INET a constant indicating that Internet protocols will be used INADDR_ANY a constant meaning any (Internet) address in this context: any own Internet address

Byte Order Different machines may have different representation of multi-byte values Consider a 16-bit integer: made up of 2 bytes address A+1 high-order byte address A low-order byte little-endian byte order MSB 16-bit value LSB high-order byte low-order byte address A address A+1 big-endian byte order

Byte Order: Storing 32-bit 0x0A0B0C0D Assuming 8-bit (one byte) atomic elements big endian: the most significant byte (MSB), 0x0A, is stored on the lowest memory address the least significant byte (LSB), 0x0D, is stored on the highest memory address increasing memory addresses 0x0A 0x0B 0x0C 0x0D little endian: 0x0A is stored on the highest memory address 0x0D is stored on the lowest memory address increasing memory addresses 0x0D 0x0C 0x0B 0x0A

Byte Order: IP address example IPv4 host address: represents a 32-bit address writtenon paper ( dotted decimal notation ): 129.240.71.213 binary in bits: 10000001 11110000 01000111 10001011 hexadecimal in bytes: 0x81 0xf0 0x47 0x8b Big-endian ( normal left to right): one 4 byte int on PowerPC, POWER, Sparc, : Little-endian: one 4 byte int on x86, StrongARM, XScale, : 0x81f0478b 0x8b47f081 Network byte order: 0x81f0478b

Byte Order: Translation Byte order translation makes communication over several platforms possible htons() / htonl() host-to-network short / long translate a 16 / 32-bit integer value to network format ntohs() / ntohl() network-to-host short/long translate a 16 / 32-bit integer value to host format Little-endian (x86 etc.): ntohl(0x81f0478b) == 0x8b47f081 Big-endian (PowerPC etc.): ntohl(0x81f0478b) == 0x81f0478b

Presentation and Numeric Address Formats The network does not interpret the dotted decimal notation presentation format needs a numeric binary format in network byte order inet_pton() translate the text string to a numeric binary format needed by the address structure inet_ntop() inet_pton() is new for IPv6. Oldest: serveraddr.sin_addr.s_addr = inet_addr( 129.240.65.59 ); Newer: inet_aton( 129.240.65.59, &serveraddr.sin_addr); translate the (numeric binary) network address structure to a text string

How far have we gotten now? Client ü <Necessary includes> int main() { char buf[13]; ü <Declare some more data structures> <Create a socket called sd > <Identify the server that you want to contact> <Connect to the server> /* Send data */ write(sd, Hello world!, 12); /* Read data from the socket */ read(sd, buf, 12); /* Add a string termination sign, and write to the screen. */ buf[12] = \0 ; printf( %s\n, buf); Server ü <Necessary includes> int main() { char buf[13]; <Declare some more data structures> <Create a socket called request-sd > <Define how the client can connect> <Wait for a connection, and create a new socket sd for that connection> ü /* read data from the sd and write it to the screen */ read(sd, buf, 12); buf[12] = \0 ; printf( %s\n, buf ); /* send data back over the connection */ write(sd, buf, 12); } <Closing code> } <Closing code>

Binding, Listening, Accepting and Connecting Client Server /* Bind the address to the socket */ bind(request_sd, (struct sockaddr*)&serveraddr, sizeof(struct sockaddr_in); /* Connect */ connect( sd, (struct sockaddr*)&serveraddr, sizeof(struct sockaddr_in)); /* Activate listening on the socket */ listen(request_sd, SOMAXCONN); /* Wait for connection */ clientaddrlen = sizeof(struct sockaddr_in); sd = accept(request_sd, (struct sockaddr*)&clientaddr, &clientaddrlen);

Some details about the previous slides bind( int sfd, struct sockaddr *a, socklen_t al ) a machine can have several addresses (several network cards, loopback, ) assign a name tells the socket on the server side which local protocol (i.e., IP address and port number) to listen to listen( int sfd, int backlog ) prepares the server for listening to connect requests, and initializes a queue for connect requests (à passive) the second parameter (SOMAXCONN) defines how long the queue(s) should be

More details sd = accept( int sfd, struct sockaddr *a, socklen_t *al ) take the first connect request from the connect request queue wait for the connect request to arrive if the queue is empty returns a new socket that the server can use to communicate with the client a (clientaddr) contains information about the client al must be initialized, so accept knows size of a connect( int sfd, struct sockaddr *serv_a, socklen_t al ) connects client socket to a server that is specified in the address structure a three-way handshake is initiated for TCP possible errors ETIMEDOUT no response (after several tries) and timer expired ECONNREFUSED server not running or not allowed to connect EHOSTUNREACH HOST not reachable ENETUNREACH NET not reachable

Closing of Sockets Client Server /* Close the socket */ close(sd); /* Close both sockets */ close(sd); close(request_sd); Note that the semantics of close depends On the kind of protocol Some possible extra settings (similar for file descriptors used to operate on disk ) All data that has not been read yet may be thrown away

Complete Client Client #include <netinet/in.h> #include <sys/socket.h> #include <netdb.h> #include <stdio.h> #include <string.h> int main() { /* Declarations */ struct sockaddr_in int sd; char buf[13]; serveraddr; /* Create socket */ sd = socket(pf_inet, SOCK_STREAM, IPPROTO_TCP); /* Clear address structure */ memset(&serveraddr, 0, sizeof(struct sockaddr_in)); /* Add address family */ serveraddr.sin_family = AF_INET; Client ctd. } /* Add IP address of vor.ifi.uio.no */ inet_pton(af_inet, 129.240.65.59, &serveraddr.sin_addr); /* Add the port number */ serveraddr.sin_port = htons(2009); /* Connect */ connect(sd, (struct sockaddr*)&serveraddr, sizeof(struct sockaddr_in)); /* Send data */ write(sd, Hello world!, 12 ); /* Read data */ read(sd, buf, 12 ); /* add string end sign, write to screen*/ buf[12] = \0 ; printf( %s\n, buf); /* Close socket */ close(sd);

Complete Server Server #include <netinet/in.h> #include <sys/socket.h> #include <netdb.h> #include <stdio.h> #include <string.h> int main() { /* Declarations */ struct sockaddr_in struct sockaddr_in int clientaddrlen; int request_sd, sd; char buf[13]; serveraddr; clientaddr; /* Create socket */ request_sd = socket(pf_inet, SOCK_STREAM, IPPROTO_TCP); /* Fill in the address structure */ memset(&serveraddr, 0, sizeof(struct sockaddr_in)); serveraddr.sin_family = AF_INET; serveraddr.sin_addr.s_addr = INADDR_ANY; serveraddr.sin_port = htons(2009); Server ctd. } /* Bind address to socket */ bind(request_sd, (struct sockaddr*)&serveraddr, sizeof(struct sockaddr_in)); /* Activate connect request queue */ listen(request_sd, SOMAXCONN); /* Receive connection */ clientaddrlen = sizeof(struct sockaddr_in); sd = accept(request_sd, (struct sockaddr*)&clientaddr, &clientaddrlen); /* Read data from socket and write it */ read(sd, buf, 12); buf[12] = \0 ; printf( %s\n, buf); /* Send data back over connection */ write(sd, buf, 12); /*Close sockets */ close(sd); close(request_sd);

Summary of Socket Functions for our Elementary TCP Client-Server Server socket() bind() Client listen() accept() socket() connect() read() write() write() read() close() close()

Compilation of these socket programs The example can be downloaded from the web pages (http://www.ifi.uio.no/~inf1060/programs/client-server-example) For testing, run server on vor (or change the address in the client) and start client on another machine Testing on one host: use 127.0.0.1 Note for BSD / Mac systems: #include <sys/types.h>

Complete Server Server... int main() { /* Declarations */... /* Create socket */ request_sd = socket(...); Server ctd. /* Receive connection */ sd = accept(...); /* Process the request*/... /*Close sockets */ close(sd); /* Fill in the address structure */... /* Bind address to socket */ bind(...); /* Activate connect request queue */ listen(...); } close(request_sd); Iterative servers?

Iterative Servers Server... int main() { /* Declarations */... Server ctd. for (;;) { /* Receive connection */ sd = accept(...); /* Process the request*/... /* Create socket */ request_sd = socket(...); /* Fill in the address structure */... /* Bind address to socket */ bind(...); /* Activate connect request queue */ listen(...); } } /*Close sockets */ close(sd); close(request_sd); Concurrent servers?

Concurrent Iterative Servers Server... int main() { /* Declarations */... pid_t pid; /* Create socket */ request_sd = socket(...); /* Fill in the address structure */... /* Bind address to socket */ bind(...); /* Activate connect request queue */ listen(...); Server ctd. } for (;;) { /* Receive connection */ sd = accept(...); } if ((pid = fork()) == 0) { close(request_sd); /* Process the request*/... } /*Close sockets */ close(sd); exit(0) /*Close sockets */ close(sd); close(request_sd);

Select Problems with these examples: iterative: cannot serve more than one socket at once concurrent: overhead (a process per socket) Solution: functions that tell you when a socket becomes available (select, poll) int select(int nfds, fd_set *restrict readfds, fd_set *restrict writefds,fd_set *restrict errorfds, struct timeval *restrict timeout) check whether fd s (sockets) from the nfds set are available for reading (readfds), writing (writefds), or have exceptional conditions pending (errorfds) Null argument: don t check. Timeout = time limit for check (Null = block). result is given by changing readfds / writefds / errorfds

Select usage and macros Select usage Declare and initialize fd_set; add relevant sockets to fd_set; give select a copy of fd_set for every operation of interest (read/write/exceptional); loop through copies to take action Preparing fd_set is done with some macros FD_CLR(fd, &fdset) removes the socket descriptor fd from the socket descriptor set fdset FD_ISSET(fd, &fdset) returns nonzero if socket descriptor fd is a member of fdset; else 0 FD_SET(fd, &fdset) adds socket descriptor fd to fdset FD_ZERO(&fdset) initializes fdset to 0, representing the empty set FD_SETSIZE - max. number of FDs; use this as the first parameter for select

Complete Select-based Server Server #include <netinet/in.h> #include <sys/socket.h> #include <netdb.h> #include <stdio.h> #include <string.h> #include <time.h> int main() { /* Declarations */ struct sockaddr_in serveraddr; struct sockaddr_in clientaddr; int clientaddrlen, i, rc; int request_sd, sd[2], numsocks, maxsocks; char buf[13]; fd_set fds, readfds; struct timeval timeout; numsocks = 0; maxsocks = 2; timeout.tv_sec = 20; timeout.tv_usec = 0; Server ctd. /* Fill in the address structure */ memset(&serveraddr, 0, sizeof(struct sockaddr_in)); serveraddr.sin_family = AF_INET; serveraddr.sin_addr.s_addr = INADDR_ANY; serveraddr.sin_port = htons(2009); /* Bind address to socket */ bind(request_sd, (struct sockaddr*)&serveraddr, sizeof(struct sockaddr_in)); /* Activate connect request queue */ listen(request_sd, SOMAXCONN); /* Initialize fd set */ FD_ZERO(&fds); FD_SET(request_sd, &fds); Test with e.g. two clients! /* Create socket */ request_sd = socket(pf_inet, SOCK_STREAM, IPPROTO_TCP);

Complete Select-based Server ctd. Server ctd. for (;;) { readfds=fds; rc=select(fd_setsize, &readfds, NULL, NULL, &timeout); /* Something went wrong */ if (rc<0) return -1; /* Nothing happened,select continued */ if (rc==0) { printf("timeout!\n"); } for(i=0; i<numsocks; i++) { /* Send a response */ write(sd[i], "Server ACK!",11); /* Close sockets */ close(sd[i]); FD_CLR(sd[i], &fds); } return 0; Server ctd. } for (i = 0; i < FD_SETSIZE; i++) if(fd_isset (i, &readfds)) { if(i == request_sock) { /* new connection request */ if(numsocks < maxsocks) { sd[numsocks] = accept(request_sock, (struct sockaddr *)&clientaddr, (socklen_t *)&clientaddrlen); FD_SET(sd[numsocks], &fds); numsocks++; } else { printf( Ran out of socket space.\n"); return -1; } } else { /* data arrived on an existing socket */ read(i, buf,12); buf[12] = '\0'; printf("from socket %d: %s\n",i,buf); } } } close(request_sock);

Summary We have implemented a short program where two processes communicate over a network Next: the magic of how data is sent

Outline for select based iterative server Server socket() bind() listen() select() Client socket() Loop to accept new clients accept() connect() YOUR CODE YOUR CODE close() close()

Outline for select based iterative server Server socket() bind() listen() select() We only call accept() when the connection is from a new client. Client socket() Loop to accept new clients accept() connect() YOUR CODE YOUR CODE close() close()

Literature Berkeley UNIX System Calls and Interprocess Communication, Lawrence Besaw, University of Wisconsin is available through the course web pages Many books: Kurose/Ross, Computer Networking: A Top-Down Approach Featuring the Internet, 2 nd ed., Addison-Wesley Andrew Tanenbaum, Computer Networks, 4 th ed., Prentice Hall W. Richard Stevens, Unix Network Programming Networking APIs: Sockets and XTI, volume 1, 2 nd ed., Prentice Hall