W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2013

Re: DOM: Futures

From: Jake Verbaten <raynos2@gmail.com>
Date: Thu, 28 Mar 2013 15:06:16 -0700
Message-ID: <CAMCMjp2DhQL3mPRsQzERTGNNOAptNbc41V8vsBvpvUjS9sqrZQ@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, "www-dom@w3.org" <www-dom@w3.org>
What are the semantics for the IO a Future does?

Does it start doing an asynchronous operation immediately?
Does it start doing an asynchronous operation once then or accept or done
is called?

Is a future a lazy representation of the asynchronous result?
Or is it simply an object on which you can put glorified event listeners
for success & failure?

On Thu, Mar 28, 2013 at 2:49 PM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Thu, Mar 28, 2013 at 9:35 PM, Tab Atkins Jr. <jackalmage@gmail.com>
> wrote:
> > I'm very interested in rewriting some of the explanatory text around
> > this, because right now it's very difficult to figure out what the
> > exact details and workings of Futures are.  I can handle this through
> > PRs.
> Sounds excellent! What's there is just the algorithms and API. What's
> needed is an introduction and some explanatory text for other
> specifications that wish to use futures. Oh, and domintro boxes that I
> will add at some point. I admit though that my strong point is model +
> API with a focus on implementations (and tests written for them) that
> need to behave identically, not so much explanatory text. I find it
> really hard to stay precise, concise, and clear in such text.
> --
> http://annevankesteren.nl/
Received on Thursday, 28 March 2013 22:06:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:20 UTC