-
Notifications
You must be signed in to change notification settings - Fork 285
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.
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
Use official SDK as low-level implementation, or clarify advantages of not doing so #263
Comments
👍 |
We've moved over to the official AWS SDK, and we've been pretty happy. |
@TooTallNate Can you or a teammate weigh on this one? Not sure who all is on the Owner/Collaborator roster. |
I don't know if it was on purpose, but andrewrk would say it's a great choice to avoid the official SDK. See: andrewrk/node-s3-client#129 |
@avimar doesn't he advocate the exact opposite?
And:
|
@adambuczynski Uhm. That's what I meant. I'm not sure why I worded it that way! |
I think it makes sense to either use the official AWS SDK as the actual implementation of talking to AWS, or clarify the advantages of avoiding that implementation. It would also be helpful to understand whether the goal is to pursue new features, or just maintain knox for existing apps on the assumption that most users are migrating to the SDK.
I'm suggesting these questions be addressed in the documentation.
The text was updated successfully, but these errors were encountered: