On Sun, Sep 8, 2013 at 8:43 PM, TJ Marbois <[email protected]> wrote: > Ben > > ok thanks.. yea I was tinkering with them and saw some strange returns - and > wasn't sure how to interpret them... ie: some functions being tracked and > others ignored - I figured it must be some internal info that is not > available to the regular node user. > > I was hoping to find a way to examine the event cue - at least enough to see > whats been placed there from my running program and in what order those > things will be executed once the cue is started.
If we're talking asynchronous I/O here, then there is usually no clear order of events. > Is there any way to do this at all? Or are there plans in the future to > allow something like this? Right now not easily but things may get better in v0.12. There is an in-progress pull request[1] that adds a kind of AOP interceptor API that makes it easy to track callbacks into JS land. Completion callbacks are only half the story though. The other half is tracking asynchronous I/O requests but that's something you can do with good old monkey-patching. I expect to see npm modules show up for that minutes after the PR lands. [1] https://github.com/joyent/node/pull/6011 -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
