Feature Request: Streaming Response

[x2764tech]

As part of a project I'm working on, I'd like to use this library to download form data to files.
I really like that the API adds a load of useful fields to the export_records method, and I'd like to continue to use that.
However, I'd also like not to have to load the entire response into memory, as I don't know how large the responses will get for our 20,000+ cohort.
Is there a way to implement the Body Content Workflow, or would this require a lot of work?

[pwildenhain]

I think this could be a great contribution. I don't currently have the bandwidth, but you're welcome to take a crack at it 👍🏻

A potential hack in the meantime could be using the fields parameter in export_records to export just the record_id field for the whole project. Then from there you can manually chunk your requests to, say, 1000 records at a time for a 20,000 record cohort, by passing a list of records to the records parameter in export_records.