- Berkeley sockets
The Berkeley sockets
application programming interface(API) comprises a library for developing applications in the C programming language that perform inter-process communication, most commonly across a computer network.
Berkeley sockets (also known as the BSD socket API) originated with the 4.2BSD
Unix operating system(released in 1983) as an API. Only in 1989, however, could UC Berkeley release versions of its operating system and networking library free from the licensing constraints of AT&T's copyright-protected Unix.
The Berkeley socket API forms the "
de facto" standard abstraction for network sockets. Most other programming languages use an interface similar to the C API.
Transport Layer Interface(TLI) API offers an alternative to the socket API. However, the Berkeley socket API predominates convincingly in popularity and in the number of implementations.
Berkeley socket interface
The Berkeley socket interface, an API, allows communications between hosts or between processes on one computer, using the concept of an "internet socket". It can work with many different I/O devices and drivers, although support for these depends on the operating-system implementation. This interface implementation is implicit for TCP/IP, and it is therefore one of the fundamental technologies underlying the
Internet. It was first developed at the University of California, Berkeleyfor use on Unix systems. All modern operating systems now have some implementation of the Berkeley socket interface, as it became the standard interface for connecting to the Internet.
Programmers can make the socket interfaces accessible at three different levels, most powerfully and fundamentally at the raw socket level. Very few applications need the degree of control over outgoing communications that this provides, so raw sockets support was intended to be available only on computers used for developing Internet-related technologies. In recent years, most operating systems have implemented support for it anyway, including Windows XP.
The header files
The Berkeley socket development library has many associated header files. They include:
:: Core BSD socket functions and data structures.:;
:: PF_INET and PF_INET6 address/protocol families. Widely used on the Internet, these include IP addresses and TCP and UDP port numbers.:;
:: PF_UNIX/PF_LOCAL address family. Used for local communication between programs running on the same computer. Not used on networks.:;
:: Functions for manipulating numeric IP addresses.:;
:: Functions for translating protocol names and host names into numeric addresses. Searches local data as well as DNS.
TCP provides the concept of a connection. A process creates a TCP socket by calling the
socket()function with the parameters
Setting up a simple TCP server involves the following steps:
* Creating a TCP socket, with a call to
* Binding the socket to the listen port, with a call to
bind(). Before calling
bind(), a programmer must declare a
sockaddr_instructure, clear it (with
memset()), and the
PF_INET6), and fill its
sin_port(the listening port, in
network byte order) fields. Converting a
short intto network byte order can be done by calling the function
htons()(host to network short).
* Preparing the socket to listen for connections (making it a listening socket), with a call to
* Accepting incoming connections, via a call to
accept(). This blocks until an incoming connection is received, and then returns a socket descriptor for the accepted connection. The initial descriptor remains a listening descriptor, and
accept()can be called again at any time with this socket, until it is closed.
* Communicating with the remote host, which can be done through
* Eventually closing each socket that was opened, once it is no longer needed, using
close(). Note that if there were any calls to
fork(), each process must close the sockets it knew about (the kernel keeps track of how many processes have a descriptor open), and two processes should not use the same socket at once.
Setting up a TCP client involves the following steps:
* Creating a TCP socket, with a call to
* Connecting to the server with the use of
connect(), passing a
sockaddr_instructure with the
sin_portset to the port the endpoint is listening (in network byte order), and
sin_addrset to the IPv4 or IPv6 address of the listening server (also in network byte order.)
* Communicating with the server by using
* Terminating the connection and cleaning up with a call to
close(). Again, if there were any calls to
fork(), each process must
UDP consists of a
connectionlessprotocol with no guarantee of delivery. UDP packets may arrive out of order, become duplicated and arrive more than once, or even not arrive at all. Due to the minimal guarantees involved, UDP has considerably less overhead than TCP. Being connectionless means that there is no concept of a stream or connection between two hosts, instead, data arrives in datagrams ( Datagram Sockets).
UDP address space, the space of UDP port numbers (in ISO terminology, the
TSAPs), is completely disjoint from that of TCP ports.
Code may set up a UDP server on port 7654 as follows:
bind() binds the socket to an address/port pair.
This infinite loop receives any UDP datagrams to port 7654 using recvfrom(). It uses the parameters:
* pointer to buffer for data
* size of buffer
* flags (same as in read or other receive socket function)
* address struct of sending peer
* length of address struct of sending peer.
A simple demo to send a UDP packet containing "Hello World!" to address 127.0.0.1, port 7654 might look like this:
In this code,
bufferprovides a pointer to the data to send, and
buffer_lengthspecifies the size of the buffer contents.
socket()creates an endpoint for communication and returns a descriptor.
socket()takes three arguments:
* domain, which specifies the protocol family of the created socket. For example:
PF_INETfor network protocol
PF_UNIXfor local socket (using a file).
* type, one of:
SOCK_STREAM(reliable stream-oriented service or
SOCK_DGRAM(datagram service or
SOCK_SEQPACKET(reliable sequenced packet service), or
SOCK_RAW(raw protocols atop the network layer).
* protocol, usually set to
IPPROTO_IP, which is defined as 0, to represent the default
transport protocolfor the specified domain and type values (TCP for
SOCK_STREAM, UDP for those
SOCK_DGRAM), but which can also explicitly specify a protocol. These protocols are specified in
The function returns -1 if an error occurred. Otherwise, it returns an integer representing the newly-assigned descriptor.
gethostbyname() and gethostbyaddr()
gethostbyaddr()functions each return a pointer to an object of type struct hostent, which describes an internet host referenced by name or by address, respectively. This structure contains either the information obtained from a name server (ex: named), or broken-out fields from a line in /etc/hosts. If the local name server is not running these routines do a lookup in /etc/hosts. The functions take the following arguments:
* name, which specifies the name of the host. For example: www.wikipedia.org
* addr, which specifies a pointer to a struct in_addr containing the address of the host.
* len, which specifies the length, in bytes, of addr.
* type, which specifies the domain type of the host address. For example: PF_INET
The functions return a NULL pointer in case of error, in which case the external integer h_errno may be checked so see whether this is a temporary failure or an invalid or unknown host. Otherwise a valid struct hostent * is returned.
connect()It returns an integer representing the error code: 0 represents success, while -1 represents an error.
Certain types of sockets are "connectionless", most commonly
user datagram protocolsockets. For these sockets, connect takes on a special meaning: the default target for sending and receiving data gets set to the given address, allowing the use of functions such as send() and recv() on connectionless sockets.
bind()assigns a socket an address. When a socket is created using
socket(), it is given an address family, but not assigned an address. Before a socket may accept incoming connections, it must be bound.
bind()takes three arguments:
sockfd, a descriptor representing the socket to perform the bind on
serv_addr, a pointer to a
sockaddrstructure representing the address to bind to.
socklen_tfield representing the length of the
sockaddrstructure.It returns 0 on success and -1 if an error occurs.
listen()prepares a bound socket to accept incoming connections. This function is only applicable to the
SOCK_SEQPACKETsocket types. It takes two arguments:
sockfd, a valid socket descriptor.
backlog, an integer representing the number of pending connections that can be queued up at any one time. The operating system usually places a cap on this value.Once a connection is accepted, it is dequeued. On success, 0 is returned. If an error occurs, -1 is returned.
accept()is used to accept a connection request from a remote host. It takes the following arguments:
sockfd, the descriptor of the listening socket to accept the connection from.
cliaddr, a pointer to the sockaddr structure that
accept()should put the client's address information into.
addrlen, a pointer to the
socklen_tinteger that will indicate to
accept()how large the sockaddr structure pointed to by
socklen_tinteger then indicates how many bytes of the
cliaddrstructure were actually used.
The function returns a socket corresponding to the accepted connection, or -1 if an error occurs.
Blocking "vs." nonblocking
Berkeley sockets can operate in one of two modes: blocking or non-blocking. A "blocking" socket will not return control until it has sent (or received) all the data specified for the operation. This is true only in Linux systems. In other systems, such as FreeBSD, it is normal for a blocking socket not to send all the data. Always check the return value to find out how many bytes have been sent/received. It’s up to you to send the rest of the string [http://beej.us/guide/bgnet/] . It also may cause problems if a socket continues to listen: a program may hang as the socket waits for data that may never arrive.
A socket is typically set to blocking or nonblocking mode using the
The system will not release the resources allocated by the
socket()call until a
close()call occurs. This is especially important if the
connect()call fails and may be retried. Each call to
socket()must have a matching call to
close()in all possible execution paths. Include
for the close function.
When an issue to the
close()system call is made only the interface to the socket gets closed, not the socket itself. It is up to the kernel to close the socket. Sometimes, the socket may go into a
TIME_WAITstate, on the server side, for up to 4 minutes. [http://www.softlab.ntua.gr/facilities/documentation/unix/unix-socket-faq/unix-socket-faq-4.html#ss4.2]
Unix domain socket
Winsock, the Berkeley sockets-based application programming interfacefor networking on Microsoft Windows
The "de jure" standard definition of the Sockets interface is contained in the POSIX standard, known as:
* IEEE Std. 1003.1-2001 Standard for Information Technology -- Portable Operating System Interface (POSIX).
* Open Group Technical Standard: Base Specifications, Issue 6, December 2001.
* ISO/IEC 9945:2002
Information about this standard and ongoing work on it is available from [http://www.opengroup.org/austin/ the Austin website] .
The IPv6 extensions to the base socket API are documented in RFC 3493 and RFC 3542.
*Unix Manual Pages
** [http://www.die.net/doc/linux/man/man2/accept.2.html accept(2)]
** [http://www.die.net/doc/linux/man/man2/connect.2.html connect(2)]
* [http://beej.us/guide/bgnet/ Beej's Guide to Network Programming] - 2007
* [http://www.developerweb.net/forum/forumdisplay.php?f=70 UnixSocket FAQ]
* [http://xzdev.com/random_ip_cpp.html Get system IP list - C++ Example]
* [http://heather.cs.ucdavis.edu/~matloff/Networks/Intro/NetIntro.pdf quick TCP-IP NetIntro with C examples]
* [http://msdn2.microsoft.com/en-us/library/ms740096.aspx Porting Berkeley Socket programs to Winsock] - Microsoft's documentation.
* [http://www.softlab.ntua.gr/facilities/documentation/unix/unix-socket-faq/unix-socket-faq.html Programming UNIX Sockets in C - Frequently Asked Questions] - 1996
* [http://www.linuxjournal.com/article/2333 Linux network programming] - "
Linux Journal", 1998
Wikimedia Foundation. 2010.
Look at other dictionaries:
Berkeley Sockets — Les Berkeley sockets, que l on pourrait traduire par « connecteurs réseau de Berkeley », représentent une interface de programmation pour les communications entre processus Interprocess communication . Elles ont été introduites pour… … Wikipédia en Français
Berkeley sockets — Les Berkeley sockets, que l on pourrait traduire par « connecteurs réseau de Berkeley », représentent une interface de programmation pour les communications entre processus Interprocess communication . Elles ont été introduites pour… … Wikipédia en Français
Berkeley Software Distribution — Infobox OS name = BSD Unix caption = developer = CSRG, UC Berkeley family = Unix like source model = Open source latest release version = 4.4 Lite2 latest release date = 1995 kernel type = Monolithic license = BSD licenses working state =… … Wikipedia
Berkeley Software Distribution Sockets — (BSD) Layer five of the OSI model … IT glossary of terms, acronyms and abbreviations
Prise (structure de données logicielle) — Berkeley sockets Les Berkeley sockets, que l on pourrait traduire par « connecteurs réseau de Berkeley », représentent une interface de programmation pour les communications entre processus Interprocess communication . Elles ont été… … Wikipédia en Français
Internet socket — In computer networking, an Internet socket or network socket is an endpoint of a bidirectional inter process communication flow across an Internet Protocol based computer network, such as the Internet. The term Internet sockets is also used as a… … Wikipedia
Winsock — In computing, the Windows Sockets API, which was later shortened to Winsock, is a technical specification that defines how Windows network software should access network services, especially TCP/IP. It defines a standard interface between a… … Wikipedia
STREAMS — In computer networking, STREAMS is the native framework in Unix System V for implementing character devices.STREAMS was designed as a modular architecture for implementing full duplex, bidirectional character I/O between kernel or user space… … Wikipedia
Socket — Pour l’article homophone, voir Socquette. Cette page d’homonymie répertorie les différents sujets et articles partageant un même nom. Socket (mot anglais qui signifie prise) est un terme informatique qui peut avoir plusieurs significations… … Wikipédia en Français
Raw socket — In computer networking, a raw socket is a socket that allows direct access to packet s headers. Due to the fact that raw sockets allow users to craft packets headers, their power can be abused to perform attacks such as IP address spoofing in… … Wikipedia