Change Instance

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

{
    "unit": "https://weblate.info.ucl.ac.be/api/units/37501/?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.180904+02:00",
    "action": 59,
    "target": "Using names solves these problems and provides additional benefits. If the clients are configured with the name of the server, they will query the name service before contacting the server. The name service will resolve the name into the corresponding address. If a server process needs to move from one physical server to another, it suffices to update the name to address mapping on the name service to allow all clients to connect to the new server. The name service also enables the servers to better sustain the load. Assume a very popular server which is accessed by millions of users. This service cannot be provided by a single physical server due to performance limitations. Thanks to the utilization of names, it is possible to scale this service by mapping a given name to a set of addresses. When a client queries the name service for the server's name, the name service returns one of the addresses in the set. Various strategies can be used to select one particular address inside the set of addresses. A first strategy is to select a random address in the set. A second strategy is to maintain information about the load on the servers and return the address of the less loaded server. Note that the list of server addresses does not need to remain fixed. It is possible to add and remove addresses from the list to cope with load fluctuations. Another strategy is to infer the location of the client from the name request and return the address of the closest server.",
    "id": 14720,
    "action_name": "String updated in the repository",
    "url": "https://weblate.info.ucl.ac.be/api/changes/14720/?format=api"
}