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

thread/context storage #3

Open

grawk opened this issue Jun 18, 2017 · 0 comments

Owner

grawk commented Jun 18, 2017 •

edited

CLS more or less "state of the art" for maintaining context within continuations

continuation-local-storage: https://github.com/othiym23/node-continuation-local-storage
blog post on "perils" of CLS: http://asim-malik.com/the-perils-of-node-continuation-local-storage/
good case study of CLS: https://datahero.com/blog/2014/05/22/node-js-preserving-data-across-async-callbacks/
Forrest Norvell (author) presenting on CLS: https://www.youtube.com/watch?v=xyjvFBTyFSE
CLS issue. losing context in express session middleware: othiym23/node-continuation-local-storage#29
summary of CLS gotchas: othiym23/node-continuation-local-storage#59

not sure if async_hooks are a possible solution to "thread storage" or not

Node.js async_hooks doc: https://nodejs.org/api/async_hooks.html
Node.js 8 announcement (includes bit on async_hooks): https://medium.com/the-node-js-collection/node-js-8-big-improvements-for-the-debugging-and-native-module-ecosystem-58454861f2fc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment