write_added_to.json
The JSON file of the “An Agreement Received and Added to without a Byte Moved” example. A maintenance agreement somebody else sent, with a signature area, a date and a line of one's own laid over its last page, an annex added after it and an empty place to sign over the signature area, every byte of the agreement left where it was.
This file is a request: an application sends it over the network to the server, which creates the PDF and sends it back. It creates the same page as the Rust and Python versions of this example. A request names every file it uses, never its content; the call carries the request and the files together. A font the server already holds, such as DejaVuSans, is named with nothing attached. Send the request to the address the API page gives.
What This Example Is For
A supplier sends a maintenance agreement as a PDF of two pages. It has to go back with a signature area, the date, a line saying who signs, and an annex of one page at the end. Opening the agreement and writing it out again would give back a different file: a signature it already carried would no longer hold, and nobody could prove the wording is still the one that was sent.
What This Example Shows
- Every byte of the received file left where it was.
- A page's worth of additions laid over a page that already exists.
- A page added at the end, counted like the others.
- An empty place to sign added over the signature area, in a section of its own.