optimize file based streams

[aajtodd]

It's not particularly efficient to have to launch a coroutine and proxy an SdkByteReadChannel to CRT. We should probably consider special casing file inputs such that we don't have to cross the JNI boundary for signing and uploading content.

See awslabs/aws-crt-java#308 which blocks this. We would also need a way to get at the file through HttpBody, see https://github.com/awslabs/smithy-kotlin/issues/297 for some ideas.

[github-actions]

This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to provide a comment or open a new issue.

[aajtodd]

We've significantly refactored the I/O model as well as implemented signing directly in Kotlin since this issue was opened. Closing as there is no signs this is actually any kind of bottleneck, we can always re-evaluate with concrete use cases/issues if that isn't the case.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.