I don't think that's a great API, it makes it impossible to download
files that are larger than the amount of RAM currently available.
That's part of why it's called "simple". But I suppose there does need to be a way to provide piece-by-piece handling in the main API.
> where source can be a bytevector, string, or input port.
What exactly is source, again? The request body to send?
Yes, request-body is a better term.
As noted on #chicken, there needs to be some way to retrieve returned results in pieces so they can be bigger than available memory. I haven't seen a good way to do that yet.