NodeUp: A continuation-local-storage Show

[dshaw]

3/27/14 at 11:00 AM PT

NodeUp #61

Alternate title: "NodeUp: An AsyncListener Show"

With:

• @dshaw
• @othiym23‎
• @trevnorris
• @dazld
• @FredKSchott

Topics:

• continuation-local-storage all the things!
  • Why Forrest, why?
  • and how?
  • What now?
  • context: core module to manage generic contexts for async call chains nodejs/node-v0.x-archive#5243
  • https://github.com/othiym23/node-continuation-local-storage
  • http://fredkschott.com/post/2014/02/conquering-asynchronous-context-with-cls/
• Async Listeners
  • https://github.com/othiym23/async-listener
  • implement domain-like hooks (asynclistener) for userland nodejs/node-v0.x-archive#6011
  • https://github.com/joyent/node/blob/master/doc/api/process.markdown#async-listeners

[othiym23]

+1, although I think it would be most interesting to talk about asyncListeners and the new event listener stuff that @trevnorris is hacking on, with CLS being an application of the API(s). Also, it would be cool to get @dazld to talk a little about his experiences with CLS as an end user.

[dshaw]

Sounds great. @dazld, what do you think? You interested in coming on @nodeup?

[creationix]

sounds like fun

On Sat, Nov 16, 2013 at 11:39 PM, Daniel Shaw notifications@github.comwrote:

[tentatively] December 2013 NodeUp TBD

With:

• @dshaw https://github.com/dshaw
• @othiym23 https://github.com/othiym23‎
• @trevnorris https://github.com/trevnorris
• @creationix https://github.com/creationix

Topics:

• continuation-local-storage all the things!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/20
.

[trevnorris]

As long as it's after Node Summit, I'm cool with it. :)

[dazld]

hey guys! sure, would love to!

[dazld]

We're using cls for this kind of stuff:

• Abstraction of values that might be 'global' in a browser context (things like cookies, auth tokens)
• Maintaining per-request state in a serving http context
• Cleanly avoid passing around tons of objects to everything, attaching things to req etc
• being able to use event listeners and know they are doing the right thing (especially WRT below..)
• Means we can have an async page rendering process on the server, especially useful in context of writing non-blocking async code, and being lazy with knowing what data we may or may not need to serve a request

[dshaw]

@dazld Excellent! Glad to have you on board.

[dshaw]

@nodeup @floating @othiym23‎ @trevnorris @creationix @dazld

Pencilled this in for Thursday 12/19. What do you all think?

[trevnorris]

@dshaw I'll be visiting family from 19-27 and won't be available during that time.

[creationix]

It's good for me.

On Mon, Dec 2, 2013 at 8:37 AM, Daniel Shaw notifications@github.comwrote:

@nodeup https://github.com/nodeup @floatinghttps://github.com/floating
@othiym23 https://github.com/othiym23‎ @trevnorrishttps://github.com/trevnorris
@creationix https://github.com/creationix @dazldhttps://github.com/dazld

Pencilled this in for Thursday 12/19. What do you all think?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/20#issuecomment-29599269
.

[dshaw]

Having @trevnorris on this show is key, so let's look to reschedule. Next dates on my NodeUp calendar are: 1/2 and 1/16.

[trevnorris]

@dshaw Right now either of those dates work for me.

[othiym23]

I'm fine for either 1/2 or 1/16!

[dazld]

Both dates in Jan are good for me too.