Change Instance

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

{
    "unit": "https://weblate.info.ucl.ac.be/api/units/37502/?format=api",
    "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/principlesnaming/?format=api",
    "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlesnaming/en/?format=api",
    "user": null,
    "author": null,
    "timestamp": "2022-09-17T01:14:27.180955+02:00",
    "action": 59,
    "target": "Mapping a single name onto a set of addresses allows popular servers to dynamically scale. There are also benefits in mapping multiple names, possibly a large number of them, onto a single address. Consider the case of information servers run by individuals or SMEs. Some of these servers attract only a few clients per day. Using a single physical server for each of these services would be a waste of resources. A better approach is to use a single server for a set of services that are all identified by different names. This enables service providers to support a large number of servers processes, identified by different names, onto a single physical server. If one of these server processes becomes very popular, it will be possible to map its name onto a set of addresses to be able to sustain the load. There are some deployments where this mapping is done dynamically in function of the load.",
    "id": 14721,
    "action_name": "String updated in the repository",
    "url": "https://weblate.info.ucl.ac.be/api/changes/14721/?format=api"
}