Currently, I put a limit of 300MB on restore requests coming through the API. To enable support for larger files, we would probably want to implement a streaming approach on the server. If we are going to respond in JSON again, we might need to implement the multipart-encoder by hand, or search for another library that can help us deliver it in an HTTP response.
If we don't go the JSON route, we may be able to use an application/octet-stream or something similar (transfer-encoding/chunked?)
Currently, I put a limit of 300MB on restore requests coming through the API. To enable support for larger files, we would probably want to implement a streaming approach on the server. If we are going to respond in JSON again, we might need to implement the multipart-encoder by hand, or search for another library that can help us deliver it in an HTTP response.
If we don't go the JSON route, we may be able to use an application/octet-stream or something similar (transfer-encoding/chunked?)
Estimated story points: 8