Changes

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "count": 28,
    "next": null,
    "previous": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlestransport/en/changes/?format=api",
    "results": [
        {
            "unit": "https://weblate.info.ucl.ac.be/api/units/37752/?format=api",
            "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/principlestransport/?format=api",
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlestransport/en/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-17T01:14:38.509871+02:00",
            "action": 59,
            "target": "The simplest approach to establish a transport connection would be to define two special control segments : `CR` (Connection Request) and `CA` (Connection Acknowledgment). The `CR` segment is sent by the transport entity that wishes to initiate a connection. If the remote entity wishes to accept the connection, it replies by sending a `CA` segment. The `CR` and `CA` segments contain `port numbers` that allow identifying the communicating applications. The transport connection is considered to be established once the `CA` segment has been received. At that point, data segments can be sent in both directions.",
            "id": 15009,
            "action_name": "String updated in the repository",
            "url": "https://weblate.info.ucl.ac.be/api/changes/15009/?format=api"
        },
        {
            "unit": "https://weblate.info.ucl.ac.be/api/units/37753/?format=api",
            "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/principlestransport/?format=api",
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlestransport/en/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-17T01:14:38.509907+02:00",
            "action": 59,
            "target": "Unfortunately, this scheme is not sufficient given the unreliable network layer. Since the network layer is imperfect, the `CR` or `CA` segments can be lost, delayed, or suffer from transmission errors. To deal with these problems, the control segments must be protected by a CRC or a checksum to detect transmission errors. Furthermore, since the `CA` segment acknowledges the reception of the `CR` segment, the `CR` segment can be protected using a retransmission timer.",
            "id": 15010,
            "action_name": "String updated in the repository",
            "url": "https://weblate.info.ucl.ac.be/api/changes/15010/?format=api"
        },
        {
            "unit": "https://weblate.info.ucl.ac.be/api/units/37754/?format=api",
            "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/principlestransport/?format=api",
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlestransport/en/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-17T01:14:38.509942+02:00",
            "action": 59,
            "target": "The last scenario is less likely, but it is important to consider it as well. The remote entity receives an old `CR` segment. It notes the connection attempt and acknowledges it by sending a `CA` segment. The initiating entity does not have a matching connection attempt and replies by sending a `REJECT`. Unfortunately, this segment never reaches the remote entity. Instead, the remote entity receives a retransmission of an older `CA` segment that contains the same sequence number as the first `CR` segment. This `CA` segment cannot be accepted by the remote entity as a confirmation of the transport connection as its acknowledgment number cannot have the same value as the sequence number of the first `CA` segment.",
            "id": 15011,
            "action_name": "String updated in the repository",
            "url": "https://weblate.info.ucl.ac.be/api/changes/15011/?format=api"
        },
        {
            "unit": "https://weblate.info.ucl.ac.be/api/units/37755/?format=api",
            "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/principlestransport/?format=api",
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlestransport/en/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-17T01:14:38.509978+02:00",
            "action": 59,
            "target": "The first point which is common between the two layers is that both use CRCs or checksums to detect transmission errors. Each segment contains a CRC/checksum which is computed over the entire segment (header and payload) by the sender and inserted in the header. The receiver recomputes the CRC/checksum for each received segment and discards all segments with an invalid CRC.",
            "id": 15012,
            "action_name": "String updated in the repository",
            "url": "https://weblate.info.ucl.ac.be/api/changes/15012/?format=api"
        },
        {
            "unit": "https://weblate.info.ucl.ac.be/api/units/37756/?format=api",
            "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/principlestransport/?format=api",
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlestransport/en/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-17T01:14:38.510021+02:00",
            "action": 59,
            "target": "Reliable transport protocols also use sequence numbers and acknowledgment numbers. While reliable protocols in the datalink layer use one sequence number per frame, reliable transport protocols consider all the data transmitted as a stream of bytes. In these protocols, the sequence number placed in the segment header corresponds to the position of the first byte of the payload in the bytestream. This sequence number allows detecting losses but also enables the receiver to reorder the out-of-sequence segments. This is illustrated in the figure below.",
            "id": 15013,
            "action_name": "String updated in the repository",
            "url": "https://weblate.info.ucl.ac.be/api/changes/15013/?format=api"
        },
        {
            "unit": "https://weblate.info.ucl.ac.be/api/units/37757/?format=api",
            "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/principlestransport/?format=api",
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlestransport/en/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-17T01:14:38.510055+02:00",
            "action": 59,
            "target": "Compared to reliable protocols in the datalink layer, reliable transport protocols encode their sequence numbers using more bits. 32 bits and 64 bits sequence numbers are frequent in the transport layer while some datalink layer protocols encode their sequence numbers in an 8 bits field. This large sequence number space is motivated by two reasons. First, since the sequence number is incremented for each transmitted byte, a single segment may consume one or several thousands of sequence numbers. Second, a reliable transport protocol must be able to detect delayed segments. This can only be done if the number of bytes transmitted during the MSL period is smaller than the sequence number space. Otherwise, there is a risk of accepting duplicate segments.",
            "id": 15014,
            "action_name": "String updated in the repository",
            "url": "https://weblate.info.ucl.ac.be/api/changes/15014/?format=api"
        },
        {
            "unit": "https://weblate.info.ucl.ac.be/api/units/37758/?format=api",
            "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/principlestransport/?format=api",
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlestransport/en/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-17T01:14:38.510090+02:00",
            "action": 59,
            "target": "The first solution to release a transport connection is to define a new control segment (e.g. the `DR` segment for Disconnection Request) and consider the connection to be released once this segment has been sent or received. This is illustrated in the figure below.",
            "id": 15015,
            "action_name": "String updated in the repository",
            "url": "https://weblate.info.ucl.ac.be/api/changes/15015/?format=api"
        },
        {
            "unit": null,
            "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/principlestransport/?format=api",
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlestransport/en/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-17T01:14:38.510122+02:00",
            "action": 0,
            "target": "",
            "id": 15016,
            "action_name": "Resource update",
            "url": "https://weblate.info.ucl.ac.be/api/changes/15016/?format=api"
        }
    ]
}