We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Jaremy will have write-up under considerations and approaches and actual user stories will shake out of that.
Good to start w/ IO file system access async.
Investigate the threadpool approach, do some experiements w/ that and integrate w/ datastore API.
Suggest looking into Libuv in Node.js: https://www.scaler.com/topics/nodejs/libuv/
The text was updated successfully, but these errors were encountered:
Okay wrote my initial thoughts, and somewhat of a summary of what @dryajov and I have been discussing: codex-storage/nim-codex#506
My brain hurts... trying to write down ideas into something cogent always seems to be draining. ;)
Sorry, something went wrong.
elcritch
No branches or pull requests
Jaremy will have write-up under considerations and approaches and actual user stories will shake out of that.
Good to start w/ IO file system access async.
Investigate the threadpool approach, do some experiements w/ that and integrate w/ datastore API.
Suggest looking into Libuv in Node.js: https://www.scaler.com/topics/nodejs/libuv/
The text was updated successfully, but these errors were encountered: