NodeUp: A continuation-local-storage Show #20
Comments
|
+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. |
|
sounds like fun On Sat, Nov 16, 2013 at 11:39 PM, Daniel Shaw notifications@git.luolix.topwrote:
|
|
As long as it's after Node Summit, I'm cool with it. :) |
|
hey guys! sure, would love to! |
|
We're using cls for this kind of stuff:
|
|
@dazld Excellent! Glad to have you on board. |
|
@nodeup @floating @othiym23 @trevnorris @creationix @dazld Pencilled this in for Thursday 12/19. What do you all think? |
ghost
assigned
|
@dshaw I'll be visiting family from 19-27 and won't be available during that time. |
|
It's good for me. On Mon, Dec 2, 2013 at 8:37 AM, Daniel Shaw notifications@git.luolix.topwrote:
|
|
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. |
|
@dshaw Right now either of those dates work for me. |
|
I'm fine for either 1/2 or 1/16! |
|
Both dates in Jan are good for me too. |
|
Just letting you know that |
|
@dshaw @othiym23 Did this show ever happen? +1 if not, I'd love to see a show about CLS and the current state of AsyncListener. I'm sure it would blow a lot of peoples minds (I know it did for me :) If you need more people, I'd be happy to share my experiences building our logging framework on top of it (see: http://fredkschott.com/post/2014/02/conquering-asynchronous-context-with-cls/) |
|
@FredKSchott Dope. We're currently waiting on @trevnorris to come back from paternity leave. Should be soon though. |
|
I love the idea of having @FredKSchott on to talk about building a logging framework with asyncListeners / CLS! |
|
👍 would listen! |
|
@trevnorris @creationix @dazld Are you available to record this Thursday (3/27) at 11am PDT? |
|
Think that time works for me. |
|
@FredKSchott @trevnorris Want to come to New Relic and record live? |
|
I'm available, although we'll need to reschedule a meeting here at NR. @janaboruta is it OK with you / Thea the other members of the New Relic community team if we use the podcasting studio? |
|
@othiym23 That's fine with us. I'll ping you on Hipchat to discuss the logistics. |
|
Count me in. |
|
+1 Count me in as well! |
|
WORDS!! Let's do this. @othiym23 @trevnorris @dazld @FredKSchott Please take a moment to drop an email to nodeup@gmail.com and dshaw@dshaw.com with your Google Docs friendly email, your Skype name and Twitter handle. Thank you! |
|
@dshaw will this be broadcasted live in any form? |
|
Sorry guys, I'm ultra busy and working 12 hours days this week to catch up. It would be irresponsible for me to add another hour to my schedule. On the bright side, @othiym23 knows fairly well my input into the conversation. I've always wanted an event source hook in node for implementing things like nextTick, domains, long stack traces, etc. I'm sad that event emitters are considered part of the event system when they are clearly sync constructs and I wish the core APIs were more callback based and less event based to make tracking this stuff easier. The edge cases are pretty nasty in the current semantics. Have fun! |
|
I know this is closed and already recorded (haven't listened to it yet), but for the sake of the argument, AsyncListener is implemented at the wrong end of the stack to properly solve issues like long-stack traces, CLS and/or async try/catch properly without shimming EE to properly set the handler context differently (at time of handler listen, not time of EE construction). FWIW, CrabDude/trycatch#32 |
|
@CrabDude Thanks for connecting the discussion. |
|
👍 |
3/27/14 at 11:00 AM PT
NodeUp #61
Alternate title: "NodeUp: An AsyncListener Show"
With:
Topics:
The text was updated successfully, but these errors were encountered: