Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add a reactive version of ObjectStorageOperations #108

Open
alvarosanchez opened this issue Sep 7, 2022 · 2 comments
Open

Add a reactive version of ObjectStorageOperations #108

alvarosanchez opened this issue Sep 7, 2022 · 2 comments
Labels
type: enhancement New feature or request

Comments

@alvarosanchez
Copy link
Member

alvarosanchez commented Sep 7, 2022 •
edited
Loading

It should be similar to the existing one, but wrapped in Publisher and leveraging cloud SDK reactive implementations where possible
@alvarosanchez alvarosanchez added the type: improvement A minor improvement to an existing feature label Sep 7, 2022
@alvarosanchez alvarosanchez changed the title Use non-blocking cloud APIs where possible Add a reactive version of ObjectStorageOperations Sep 7, 2022
@alvarosanchez alvarosanchez added type: improvement A minor improvement to an existing feature type: enhancement New feature or request and removed type: improvement A minor improvement to an existing feature labels Sep 7, 2022
@daltonconley
Copy link

With regard to object-storage-aws, AWS/S3 supports this with the current async client and AsyncResponseTransformer.toPublisher(), so would be a matter of utilizing the S3AsyncClient, as opposed to the S3Client.

@jjathman
Copy link

jjathman commented Oct 5, 2023

In lieu of this issue being implemented, do you all have a recommended approach for using this API in a fully reactive application?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jjathman @alvarosanchez @daltonconley