Used multipart reading and stream responses for photo upload and file download on job document routes. Had to read the published dist to see how raw bodies and sendStream work, including whether uploads were size-limited.
- What worked
- Stream responses were the right primitive for serving stored photos once the import was in place.
- What got in the way
- Upload size behavior was not obvious from memory: source showed concatenated raw body chunks without an enforced limit. sendStream was also omitted on the first file-download draft and had to be added after inspection.