Changes

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

{
    "count": 3,
    "next": null,
    "previous": null,
    "results": [
        {
            "unit": "https://weblate.info.ucl.ac.be/api/units/37567/?format=api",
            "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/protocolstcp/?format=api",
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolstcp/en/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-17T01:14:31.950332+02:00",
            "action": 59,
            "target": "The second path is when the host has transmitted all data. Assume that the last transmitted sequence number is `z`. Then, the host sends a  `FIN` segment with sequence number :math:`(z+1) \\pmod{2^{32}}` and enters the `FIN_WAIT1` state. In this state, it can retransmit unacknowledged segments but cannot send new data segments. It waits for an acknowledgment of its `FIN` segment (i.e. sequence number :math:`(z+1) \\pmod{2^{32}}`), but may receive a `FIN` segment sent by the remote host. In the first case, the TCP connection enters the `FIN\\_WAIT2` state. In this state, new data segments from the remote host are still accepted until the reception of the `FIN` segment. The acknowledgment for this `FIN` segment is sent once all data received before the `FIN` segment have been delivered to the user and the connection enters the `TIME\\_WAIT` state. In the second case, a `FIN` segment is received and the connection enters the `Closing` state once all data received from the remote host have been delivered to the user. In this state, no new data segments can be sent and the host waits for an acknowledgment of its `FIN` segment before entering the `TIME\\_WAIT` state.",
            "id": 14815,
            "action_name": "String updated in the repository",
            "url": "https://weblate.info.ucl.ac.be/api/changes/14815/?format=api"
        },
        {
            "unit": "https://weblate.info.ucl.ac.be/api/units/37568/?format=api",
            "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/protocolstcp/?format=api",
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolstcp/en/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-17T01:14:31.950397+02:00",
            "action": 59,
            "target": "The :math:`2*MSL` seconds delay in the `TIME\\_WAIT` state is an important operational problem on servers having thousands of simultaneously opened TCP connections [FTY99]_. Consider for example a busy web server that processes 10.000 TCP connections every second. If each of these connections remains in the `TIME\\_WAIT` state for 4 minutes, this implies that the server would have to maintain more than 2 million TCBs at any time. For this reason, some TCP implementations prefer to perform an abrupt connection release by sending a `RST` segment to close the connection [AW05]_ and immediately discard the corresponding :term:`TCB`. However, if the `RST` segment is lost, the remote host continues to maintain a :term:`TCB` for a connection that no longer exists. This optimization reduces the number of TCBs maintained by the host sending the `RST` segment but at the potential cost of increased processing on the remote host when the `RST` segment is lost.",
            "id": 14816,
            "action_name": "String updated in the repository",
            "url": "https://weblate.info.ucl.ac.be/api/changes/14816/?format=api"
        },
        {
            "unit": null,
            "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/protocolstcp/?format=api",
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolstcp/en/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-17T01:14:31.950441+02:00",
            "action": 0,
            "target": "",
            "id": 14817,
            "action_name": "Resource update",
            "url": "https://weblate.info.ucl.ac.be/api/changes/14817/?format=api"
        }
    ]
}