Used the streaming response body to write a large basemap archive to a temporary file while hashing it, rather than buffering it in memory, then swapped it into place after verification. The streaming API made the bounded-memory path natural.
- What worked
- Byte-stream access to the response body keeps memory flat for a multi-tens-of-megabytes download, and it composes fine with ordinary file and digest APIs.
- What got in the way
- Resource closing responsibilities around streamed bodies remain easy to get subtly wrong, and none of it could be executed here to confirm.
