Exit Zen
1
../../exercises/sockets.rst:4
English
Using sockets for inter-process communication
0/450 · 45
3
../../exercises/sockets.rst:52
English
The socket is a powerful abstraction as it allows processes to communicate even if they are located on different computers. In this specific cases, the inter-processes communication will go through a network.
0/2080 · 208
4
../../exercises/sockets.rst:98
English
Networked applications were usually implemented by using the :term:`socket` :term:`API`. This API was designed when TCP/IP was first implemented in the `Unix BSD`_ operating system [Sechrest]_ [LFJLMT]_, and has served as the model for many APIs between applications and the networking stack in an operating system. Although the socket API is very popular, other APIs have also been developed. For example, the STREAMS API has been added to several Unix System V variants [Rago1993]_. The socket API is supported by most programming languages and several textbooks have been devoted to it. Users of the C language can consult [DC2009]_, [Stevens1998]_, [SFR2004]_ or [Kerrisk2010]_. The Java implementation of the socket API is described in [CD2008]_ and in the `Java tutorial <http://java.sun.com/docs/books/tutorial/networking/sockets/index.html>`_. In this section, we will use the C socket API to illustrate the key concepts.
0/9290 · 929
5
../../exercises/sockets.rst:100
English
The socket API is quite low-level and should be used only when you need a complete control of the network access. If your application simply needs, for instance, to retrieve data from a web server, there are much simpler and higher-level APIs.
0/2430 · 243
6
../../exercises/sockets.rst:102
English
A detailed discussion of the socket API is outside the scope of this section and the references cited above provide a detailed discussion of all the details of the socket API. As a starting point, it is interesting to compare the socket API with the service primitives that we have discussed in the previous chapter. Let us first consider the connectionless service that consists of the following two primitives :
0/4140 · 414
7
../../exercises/sockets.rst:104
English
`DATA.request(destination,message)` is used to send a message to a specified destination. In this socket API, this corresponds to the ``send`` method.
0/1500 · 150
8
../../exercises/sockets.rst:105
English
`DATA.indication(message)` is issued by the transport service to deliver a message to the application. In the socket API, this corresponds to the return of the ``recv`` method that is called by the application.
0/2100 · 210
9
../../exercises/sockets.rst:107
English
The `DATA` primitives are exchanged through a service access point. In the socket API, the equivalent to the service access point is the `socket`. A `socket` is a data structure which is maintained by the networking stack and is used by the application every time it needs to send or receive data through the networking stack.
0/3260 · 326
10
../../exercises/sockets.rst:110
English
Sending data to a peer using a socket
0/370 · 37
12
../../exercises/sockets.rst:114
English
The ``sendto`` system call allows to send data to a peer identified by its socket address through a given socket.
0/1130 · 113
13
../../exercises/sockets.rst:120
English
The first argument is the file descriptor of the socket that we use to perform the communication. ``buf`` is a buffer of length ``len`` containing the bytes to send to the peer. The usage of ``flags`` argument is out of the scope of this section and can be set to 0. ``dest_addr`` is the socket address of the destination to which we want to send the bytes, its length is passed using the ``addrlen`` argument.
0/4100 · 410
14
../../exercises/sockets.rst:122
English
In the following example, a C program is sending the bytes ``'h'``, ``'e'``, ``'l'``, ``'l'`` and ``'o'`` to a remote process located at address ``peer_addr``, using the already created socket ``sock``.
0/2020 · 202
15
../../exercises/sockets.rst:135
English
As the ``sendto`` function is generic, this function will work correctly independently from the fact that the peer's address is defined as a path on the computer filesystem or a network address.
0/1940 · 194
16
../../exercises/sockets.rst:139
English
Receiving data from a peer using a socket
0/410 · 41
18
../../exercises/sockets.rst:144
English
The following program binds its socket to a given socket address and then waits for receiving new bytes, using the already created socket ``sock``.
0/1470 · 147
19
../../exercises/sockets.rst:173
English
Depending on the socket address family, the operating system might implicitly assign an address to an unbound socket upon a call to ``write``, ``send`` or ``sendto``. While this is a useful behavior, describing it precisely is out of the scope of this section.
0/2600 · 260
20
../../exercises/sockets.rst:175
English
Using this code, the program will read and print an arbitrary message received from an arbitrary peer who knows the program's socket address. If we want to know the address of the peer that sent us the message, we can use the ``recvfrom`` system call. This is what a modified version of ``bind_and_receive_from_peer`` is doing below.
0/3330 · 333
21
../../exercises/sockets.rst:213
English
This function is now using the ``recvfrom`` system call that will also provide the address of the peer who sent the message. As addresses are generic and can have different sizes, ``recvfrom`` also tells us the size of the address that it has written.
0/2510 · 251
22
../../exercises/sockets.rst:216
English
``connect``: connecting a socket to a remote address
0/520 · 52
24
../../exercises/sockets.rst:224
English
This system call will assign the socket ``sockfd`` to the ``addr`` remote socket address. The process can then use the ``send`` and ``write`` system calls that do not to specify the destination socket address. Furthermore, the calls to ``recv`` and ``read`` will only deliver messages sent by this remote address. This is useful when we only care about the other peer messages.
0/3770 · 377