This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Triton-private Repository". The branch, master has been updated via 2cb5b434e91a3dfcf5f221c1a83fa84ad5a5c46b (commit) from d71cd4c41957356f20cd8043238609b0d629b8a2 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 2cb5b434e91a3dfcf5f221c1a83fa84ad5a5c46b Author: Justin M Wozniak <[email protected]> Date: Fri Mar 16 16:47:36 2012 -0500 Minor changes ----------------------------------------------------------------------- Summary of changes: papers/2011/aesop/implementation.tex | 2 +- papers/2011/aesop/intro.tex | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) Diff of changes: diff --git a/papers/2011/aesop/implementation.tex b/papers/2011/aesop/implementation.tex index d78fae6..ec9f1d1 100644 --- a/papers/2011/aesop/implementation.tex +++ b/papers/2011/aesop/implementation.tex @@ -58,7 +58,7 @@ in the function. % variables, state management Because variables local to the function scope are stored on the stack and are -destroyed when returning from the function, \aesop\, as part of the +destroyed when returning from the function, \aesop, as part of the rewriting process, moves all function scope variables (and function arguments) into a context structure on the heap, transparently rewriting variable references to account for this change. A pointer to this context is diff --git a/papers/2011/aesop/intro.tex b/papers/2011/aesop/intro.tex index bc63da0..1bf6766 100644 --- a/papers/2011/aesop/intro.tex +++ b/papers/2011/aesop/intro.tex @@ -43,7 +43,7 @@ Thread scheduling and stack management are handled by the operating system. Building a multithreaded service raises a number of challenges, however. The first is determining how to provision thread resources. Threads can be assigned per client, per request, or per -underlying device operation and they may be created on demand or allocated +underlying device operation; they may be created on demand or allocated from an existing pool. Each technique or combination of techniques presents tradeoffs in scalability, performance, and readability. Yet it is difficult to transition between techniques during the development process. The second challenge @@ -109,15 +109,15 @@ operations. The contributions of this paper can be summarized as follows: \begin{itemize} -\item Description of a new programming model and language, \aesop, +\item Description of a new programming model and language, \aesop, for use in the development of distributed system software -\item Definition of new language constructs to help manage highly +\item Definition of new language constructs to help manage highly concurrent execution \item Case study comparing \aesop to five popular multithreaded and event-driven architectures, using a simple distributed service as an example \item Quantitative analysis of the code complexity of the architectures -used in the case study +used in the case study \end{itemize} The remainder of this paper is organized as follows. hooks/post-receive -- Triton-private Repository