You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Range-based downloads should be handled by the file systems. Instead of transporting large files to the ocdav layers for small ranges, these should be truncated earlier as per the functionalities provided by the fs.
The text was updated successfully, but these errors were encountered:
@butonic yep, currently we read the complete file from the file system and truncate it later. We were discussing the possibility of having this functionality in EOS so as to avoid streaming the whole file. So different file systems would handle it differently (they already do so for range-based uploads via tus), so it makes sense to move this implementation detail there.
Range-based downloads should be handled by the file systems. Instead of transporting large files to the ocdav layers for small ranges, these should be truncated earlier as per the functionalities provided by the fs.
The text was updated successfully, but these errors were encountered: