Fair enough, I'll see if I can cut the technobabble. This is a pretty abstract thing, though, and it's tough to explain concisely. Perhaps a better example?

On Aug 5, 2013, at 9:29, Mithgol <notifications@github.com> wrote:

> In doc/api/continuation_local_storage.md:
> 
> > +Continuation-local storage provides a mechanism similar to thread-local storage
> > +in threaded programming, with closures wrapped around portions of a
> > +continuation chain taking the place of mutable cells bound to thread data
> > +structures. Contexts are created on namespaces and can be be nested.
> > +
> > +Every namespace is created with a default context. The currently active
> > +context on a namespace is available via `namespace.active`.
> > +
> > +A simple rule of thumb is anywhere where you might have set a property on the
> > +`request` or `response` objects in an HTTP handler, you can (and should) now
> > +use continuation-local storage.
> > +
> > +A simple, annotated example:
> > +
> > +```javascript
> > +var cls = require('contination-local-storage');
> I've read the following:
> 
> Continuation-local storage provides a mechanism similar to thread-local storage in threaded programming, with closures wrapped around portions of a continuation chain taking the place of mutable cells bound to thread data structures.
> 
> I still don't seem to get what it is. Seriously, gportions of a continuation chain taking the place of mutable cellsh seems like greligious philosophy meets biotechh to me.
> 
> \
> Reply to this email directly or view it on GitHub.