2. cnp3-ebook
3. exercises/sockets
4. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:empty

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location
• Component and priority

	Translation	Source string	Target string
	cnp3-ebook/exercises/sockets — Czech	Using sockets for inter-process communication
	cnp3-ebook/exercises/sockets — Czech	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.
	cnp3-ebook/exercises/sockets — Czech	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.
	cnp3-ebook/exercises/sockets — Czech	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.
	cnp3-ebook/exercises/sockets — Czech	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 :
	cnp3-ebook/exercises/sockets — Czech	`DATA.request(destination,message)` is used to send a message to a specified destination. In this socket API, this corresponds to the ``send`` method.
	cnp3-ebook/exercises/sockets — Czech	`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.
	cnp3-ebook/exercises/sockets — Czech	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.
	cnp3-ebook/exercises/sockets — Czech	Sending data to a peer using a socket
	cnp3-ebook/exercises/sockets — Czech	The ``sendto`` system call allows to send data to a peer identified by its socket address through a given socket.
	cnp3-ebook/exercises/sockets — Czech	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.
	cnp3-ebook/exercises/sockets — Czech	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``.
	cnp3-ebook/exercises/sockets — Czech	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.
	cnp3-ebook/exercises/sockets — Czech	Receiving data from a peer using a socket
	cnp3-ebook/exercises/sockets — Czech	The following program binds its socket to a given socket address and then waits for receiving new bytes, using the already created socket ``sock``.
	cnp3-ebook/exercises/sockets — Czech	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.
	cnp3-ebook/exercises/sockets — Czech	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.
	cnp3-ebook/exercises/sockets — Czech	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.
	cnp3-ebook/exercises/sockets — Czech	``connect``: connecting a socket to a remote address
	cnp3-ebook/exercises/sockets — Czech	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.
	cnp3-ebook/exercises/sockets — Czech	The following program connects a socket to a remote address, sends a message and waits for a reply.
	cnp3-ebook/exercises/sockets — Czech	Creating a new socket to communicate through a network
	cnp3-ebook/exercises/sockets — Czech	Until now, we learned how to use sockets that were already created. When writing a whole program, you will have to create you own sockets and choose the concrete technology that it will use to communicate with others. In this section, we will create new sockets and allow a program to communicate with processes located on another computer using a network. The most recent standardized technology used to communicate through a network is the :term:`IPv6` network protocol. In the IPv6 protocol, hosts are identified using *IPv6 addresses*. Modern operating systems allow IPv6 network communications between programs to be done using the socket API, just as we did in the previous sections.
	cnp3-ebook/exercises/sockets — Czech	A program can use the ``socket`` system call to create a new socket.
	cnp3-ebook/exercises/sockets — Czech	The ``domain`` parameter specifies the address family that we will use to concretely perform the communication. For an IPv6 socket, the ``domain`` parameter will be set to the value ``AF_INET6``, telling the operating system that we plan to communicate using IPv6 addresses. The ``type`` parameter specifies the communication guarantees that we need. For now, we will use the type ``SOCK_DGRAM`` which allows us to send *unreliable messages*. This means that each data that we send at each call of ``sendto`` will either be completely received or not received at all. The last parameter will be set to ``0``. The following line creates a socket, telling the operating system that we want to communicate using IPv6 addresses and that we want to send unreliable messages.
	cnp3-ebook/exercises/sockets — Czech	Sending a message to a remote peer using its IPv6 address
	cnp3-ebook/exercises/sockets — Czech	Now that we created an IPv6 socket, we can use it to reach another program if we know its IPv6 address. IPv6 addresses have a human-readable format that can be represented as a string of characters. The details of IPv6 addresses are out of scope of this section but here are some examples :
	cnp3-ebook/exercises/sockets — Czech	The ``::1`` IPv6 address identifies the computer on which the current program is running.
	cnp3-ebook/exercises/sockets — Czech	The ``2001:6a8:308f:9:0:82ff:fe68:e520`` IPv6 address identifies the computer serving the ``https://beta.computer-networking.info`` website.
	cnp3-ebook/exercises/sockets — Czech	An IPv6 address often identifies a computer and not a program running on the computer. In order to identify a specific program running on a specific computer, we use a *port number* in addition to the IPv6 address. A program using an IPv6 socket is this identified using :
	cnp3-ebook/exercises/sockets — Czech	The IPv6 address of the computer
	cnp3-ebook/exercises/sockets — Czech	The port number identifying the program running on the computer
	cnp3-ebook/exercises/sockets — Czech	A program can use the ``struct sockaddr_in6`` to represent IPv6 socket addresses. The following program creates a ``struct sockaddr_in6`` that identifies the program that reserved the port number ``55555`` on the computer identified by the ``::1`` IPv6 address.
	cnp3-ebook/exercises/sockets — Czech	Now, we have built everything we need to send a message to the remote program. The ``create_socket_and_send_message`` function below assembles all the building blocks we created until now in order to send the message ``"hello"`` to the program running on port ``55555`` on the computer identified by the ``::1`` IPv6 address.
	cnp3-ebook/exercises/sockets — Czech	Note that we can reuse our ``send_hello_to_peer`` function without any modification as we wrote it to handle any kind of sockets, including sockets using the IPv6 network protocol.
	cnp3-ebook/exercises/sockets — Czech	Endianness: exchanging integers between different computers
	cnp3-ebook/exercises/sockets — Czech	Besides character strings, some applications also need to exchange 16 bits and 32 bits fields such as integers. A naive solution would have been to send the 16- or 32-bits field as it is encoded in the host's memory. Unfortunately, there are different methods to store 16- or 32-bits fields in memory. Some CPUs store the most significant byte of a 16-bits field in the first address of the field while others store the least significant byte at this location. When networked applications running on different CPUs exchange 16 bits fields, there are two possibilities to transfer them over the transport service :
	cnp3-ebook/exercises/sockets — Czech	send the most significant byte followed by the least significant byte
	cnp3-ebook/exercises/sockets — Czech	send the least significant byte followed by the most significant byte
	cnp3-ebook/exercises/sockets — Czech	Besides 16 and 32 bit words, some applications need to exchange data structures containing bit fields of various lengths. For example, a message may be composed of a 16 bits field followed by eight, one bit flags, a 24 bits field and two 8 bits bytes. Internet protocol specifications will define such a message by using a representation such as the one below. In this representation, each line corresponds to 32 bits and the vertical lines are used to delineate fields. The numbers above the lines indicate the bit positions in the 32-bits word, with the high order bit at position `0`.
	cnp3-ebook/exercises/sockets — Czech	Message format
	cnp3-ebook/exercises/sockets — Czech	The message mentioned above will be transmitted starting from the upper 32-bits word in network byte order. The first field is encoded in 16 bits. It is followed by eight one bit flags (`A-H`), a 24 bits field whose high order byte is shown in the first line and the two low order bytes appear in the second line followed by two one byte fields. This ASCII representation is frequently used when defining binary protocols. We will use it for all the binary protocols that are discussed in this book.
	cnp3-ebook/exercises/sockets — Czech	Exercises
	cnp3-ebook/exercises/sockets — Czech	Here are some exercises that will help you to learn how to use sockets.
	cnp3-ebook/exercises/sockets — Czech	Footnotes
	cnp3-ebook/exercises/sockets — Czech	For example, the ``htonl(3)`` (resp. ``ntohl(3)``) function the standard C library converts a 32-bits unsigned integer from the byte order used by the CPU to the network byte order (resp. from the network byte order to the CPU byte order). Similar functions exist in other programming languages.