Changes in cnp3-ebook/principles/referencemodels @ Weblate

None New alert cnp3-ebook / principles/referencemodels	Could not update the repository. a year ago
None Resource update cnp3-ebook / principles/referencemodels — English	File `locale/pot/principles/referencemodels.pot` was added. 2 years ago
None String updated in the repository cnp3-ebook / principles/referencemodels — English	English the `Presentation layer` was designed to cope with the different ways of representing information on computers. There are many differences in the way computer store information. Some computers store integers as 32 bits field, others use 64 bits field and the same problem arises with floating point number. For textual information, this is even more complex with the many different character codes that have been used [#funicode]_. The situation is even more complex when considering the exchange of structured information such as database records. To solve this problem, the Presentation layer provides a common representation of the data transferred. The :term:`ASN.1` notation was designed for the Presentation layer and is still used today by some protocols. English 762 characters edited Current translation Read only the `Presentation layer` was designed to cope with the different ways of representing information on computers. There are many differences in the way computer store information. Some computers store integers as 32 bits field, others use 64 bits field and the same problem arises with floating point number. For textual information, this is even more complex with the many different character codes that have been used [#funicode]_. The situation is even more complex when considering the exchange of structured information such as database records. To solve this problem, the Presentation layer provides a common representation of the data transferred. The :term:`ASN.1` notation was designed for the Presentation layer and is still used today by some protocols. 2 years ago
None String updated in the repository cnp3-ebook / principles/referencemodels — English	English the `Session layer`. The Session layer contains the protocols and mechanisms that are necessary to organize and to synchronize the dialogue and to manage the data exchange of presentation layer entities. While one of the main functions of the transport layer is to cope with the unreliability of the network layer, the session's layer objective is to hide the possible failures of transport-level connections to the upper layer higher. For this, the Session Layer provides services that allow establishing a session-connection, to support in-order data exchange (including mechanisms that allow recovering from the abrupt release of an underlying transport connection), and to release the connection in an orderly manner. English 721 characters edited Current translation Read only the `Session layer`. The Session layer contains the protocols and mechanisms that are necessary to organize and to synchronize the dialogue and to manage the data exchange of presentation layer entities. While one of the main functions of the transport layer is to cope with the unreliability of the network layer, the session's layer objective is to hide the possible failures of transport-level connections to the upper layer higher. For this, the Session Layer provides services that allow establishing a session-connection, to support in-order data exchange (including mechanisms that allow recovering from the abrupt release of an underlying transport connection), and to release the connection in an orderly manner. 2 years ago
None String updated in the repository cnp3-ebook / principles/referencemodels — English	English In contrast with OSI, the TCP/IP community did not spend a lot of effort defining a detailed reference model; in fact, the goals of the Internet architecture were only documented after TCP/IP had been deployed [Clark88]_. :rfc:`1122`, which defines the requirements for Internet hosts, mentions four different layers. Starting from the top, these are : English 352 characters edited Current translation Read only In contrast with OSI, the TCP/IP community did not spend a lot of effort defining a detailed reference model; in fact, the goals of the Internet architecture were only documented after TCP/IP had been deployed [Clark88]_. :rfc:`1122`, which defines the requirements for Internet hosts, mentions four different layers. Starting from the top, these are : 2 years ago
None String updated in the repository cnp3-ebook / principles/referencemodels — English	English There are different types of transport layers. The most widely used transport layers on the Internet are :term:`TCP`, that provides a reliable connection-oriented bytestream transport service, and :term:`UDP`, that provides an unreliable connection-less transport service. English 272 characters edited Current translation Read only There are different types of transport layers. The most widely used transport layers on the Internet are :term:`TCP`, that provides a reliable connection-oriented bytestream transport service, and :term:`UDP`, that provides an unreliable connection-less transport service. 2 years ago
None String updated in the repository cnp3-ebook / principles/referencemodels — English	English The network layer enables hosts to reach each others. However, different communication flows can take place between the same hosts. These communication flows might have different needs (some require reliable delivery, other not) and need to be distinguished. Ensuring an identification of a communication flow between two given hosts is the task of the `transport layer`. `Transport layer` entities exchange `segments`. A segment is a finite sequence of bytes that are transported inside one or more packets. A transport layer entity issues segments (or sometimes part of segments) as `Data.request` to the underlying network layer entity. English 639 characters edited Current translation Read only The network layer enables hosts to reach each others. However, different communication flows can take place between the same hosts. These communication flows might have different needs (some require reliable delivery, other not) and need to be distinguished. Ensuring an identification of a communication flow between two given hosts is the task of the `transport layer`. `Transport layer` entities exchange `segments`. A segment is a finite sequence of bytes that are transported inside one or more packets. A transport layer entity issues segments (or sometimes part of segments) as `Data.request` to the underlying network layer entity. 2 years ago
None String updated in the repository cnp3-ebook / principles/referencemodels — English	English An important point to note about the Physical layer is the service that it provides. This service is usually an unreliable service that allows the users of the Physical layer to exchange bits. The unit of information transfer in the Physical layer is the bit. The Physical layer service is unreliable because : English 310 characters edited Current translation Read only An important point to note about the Physical layer is the service that it provides. This service is usually an unreliable service that allows the users of the Physical layer to exchange bits. The unit of information transfer in the Physical layer is the bit. The Physical layer service is unreliable because : 2 years ago
None New alert cnp3-ebook / principles/referencemodels	Could not update the repository. 2 years ago
None New alert cnp3-ebook / principles/referencemodels	Repository outdated. 2 years ago
None New alert cnp3-ebook / principles/referencemodels	Repository outdated. 2 years ago
gegoa Removed translation cnp3-ebook / principles/referencemodels	locale/en/LC_MESSAGES/principles/referencemodels.po 3 years ago
gegoa Committed changes cnp3-ebook / principles/referencemodels — French	Committed changes 3 years ago
gegoa Translation changed cnp3-ebook / principles/referencemodels — French	English Footnotes French 4 characters edited Current translation Notes de ~~bas~~pied de page 3 years ago
gegoa New contributor cnp3-ebook / principles/referencemodels — French	New contributor 3 years ago
None New alert cnp3-ebook / principles/referencemodels	Repository has changes. 3 years ago
None New alert cnp3-ebook / principles/referencemodels	Repository has changes. 3 years ago
None New alert cnp3-ebook / principles/referencemodels	Repository has changes. 3 years ago
None New alert cnp3-ebook / principles/referencemodels	Repository has changes. 3 years ago
None New alert cnp3-ebook / principles/referencemodels	Repository has changes. 3 years ago

2 / 9

/ 9

Search

Project

Language

Action

Author username

Starting date

Ending date