Provide an option to perform in-memory encoding on upload #36
Labels
edge
enhancement
New feature or request
good first issue
Good for newcomers
hacktoberfest
help wanted
Extra attention is needed
up for grabs
We added the
hacktoberfest
label to issues we considered a good fit for 2021's Hacktoberfest. If you want to work on this issue, let us know in the discussion below, so we can remove theup for grabs
label and avoid having people working on the same issue independently, making sure no one's work goes in vain. Please also consider discussing how you would like to approach the problem, if appropriate. Thank you for contributing!The uplink library that Gateway-MT and Gateway-ST use internally has an option to perform file encoding (upload) with an in-memory buffer instead of a disk buffer. The type of buffer should be a config option for both gateways. Currently, only Gateway-MT uses it:
It would be best to port this feature into Gateway-ST as well. The context value that tells libuplink to perform in-memory encoding can be set in Gateway-ST's object layer directly for Put... functions. Since Gateway-MT imports Gateway-ST, this functionality can be essentially moved from Gateway-MT to here and re-imported.
The text was updated successfully, but these errors were encountered: