Pass to fixup definitions and add some content. #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mike-kaufman
approved these changes
Dec 20, 2017
Async-Context-Definitions.md
Outdated
| every function. Thus, from a runtime viewpoint all of the functions are | ||
| part of the same asynchronous context regardless of which (logically | ||
| is implemented using JavaScript in Node core and uses a list of timer | ||
| callbacks to track _every_ function to be executed when a given timespan has elapsed. When the timespan expires a single synchronous function is called |
There was a problem hiding this comment.
missed your 80-column goal here.
Async-Context-Definitions.md
Outdated
| program execution but requires the use of _callback_ or _promise_ based code | ||
| to ensure applications remain responsive. Thus, understanding the behavior of | ||
| an application requires understanding the execution of several blocks of code | ||
| and how their executions are related via asynchronous callback interleavings |
Async-Context-Definitions.md
Outdated
| logically responsible (according to the `host` API) | ||
| for causing the execution of a previously **linked** _g_ from context _j_ | ||
| we say _f<sub>i</sub>_ `causes` _g<sub>j</sub>_. | ||
| - **happens before** -- when a function _f_ in context _i_ is asynchronously |
There was a problem hiding this comment.
Does happens before need to be more generally defined in terms of context, and not just execution. E.g., "given two contexts fi and gj, we say fi happens before gj if and only if i < j."
Async-Context-Definitions.md
Outdated
| point in program execution. For example, the following code | ||
| A **long call stack** is a list of call-stacks that span asynchronous callback | ||
| operations. Analagous to a synchronous callstack, "Long call stacks" are | ||
| useful for programmers to answer the question of "what was the call path to a specific point in program execution. For example, the following code |
Async-Context-Definitions.md
Outdated
| ### Resource Use Monitoring with Traces | ||
| **TODO** fill this in | ||
|
|
||
| ### Long Call-Stacks from Graphs |
There was a problem hiding this comment.
I was thinking that stuff like this would be in section 5. i.e., precisely how do you solve a given problem (long stacks, CLS, async exception handling,...) given the previous definitions.
Async-Context-Definitions.md
Outdated
|
|
||
| We define the following module code that provides the needed explicit marking | ||
| of API's that are exposing asynchronous behavior from a `host` component to | ||
| - **causal** -- when the execution of a function _f_ in context _i_ is |
There was a problem hiding this comment.
for completeness here, do we want to define "execution context" as well?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.