On Thu, Apr 18, 2013 at 7:20 PM, Domenic Denicola
wrote:
> Makes sense, and thanks for clarifying!
>
> I guess my only hesitation is that promises evolved over many years, with the
> design we see in Promises/A+ today and its many implementations, including
> DOM Futures, being the result of con
On Fri, Apr 19, 2013 at 6:37 PM, Ron Buckton wrote:
>> -Original Message-
>> From: Tab Atkins Jr. [mailto:jackalm...@gmail.com]
>> Sent: Friday, April 19, 2013 5:18 PM
>> To: Kevin Gadd
>> Cc: Ron Buckton; es-discuss
>> Subject: Re: Futures (was: Request for JSON-LD API review)
>>
>> On Fr
> -Original Message-
> From: Tab Atkins Jr. [mailto:jackalm...@gmail.com]
> Sent: Friday, April 19, 2013 5:18 PM
> To: Kevin Gadd
> Cc: Ron Buckton; es-discuss
> Subject: Re: Futures (was: Request for JSON-LD API review)
>
> On Fri, Apr 19, 2013 at 4:02 PM, Kevin Gadd wrote:
>
> One si
From: Tab Atkins Jr. [mailto:jackalm...@gmail.com]
Sent: Friday, April 19, 2013 3:14 PM
>
> On Fri, Apr 19, 2013 at 2:24 PM, Ron Buckton
> wrote:
> > Progress notifications are a bit of a mixed bag for me. My first
> > implementations of Future didn’t have them, but I had a number of
> > instanc
On Fri, Apr 19, 2013 at 4:02 PM, Kevin Gadd wrote:
> I'm not sure there's a perfect solution, yeah. Cancellation is definitely
> not something you want every listener to be responsible for in a
> multiple-listener scenario - most scenarios I've dealt with are ones where a
> single task is responsi
I'm not sure there's a perfect solution, yeah. Cancellation is definitely
not something you want every listener to be responsible for in a
multiple-listener scenario - most scenarios I've dealt with are ones where
a single task is responsible for the lifetime of a future - deciding
whether to cance
On Fri, Apr 19, 2013 at 3:35 PM, Kevin Gadd wrote:
> My solution for cancellation has been to allow cancellation notifications to
> be bidirectional - that is, when you subscribe to completion notifications
> on a Future, you can also subscribe to cancellation notifications. Then it's
> possible t
My solution for cancellation has been to allow cancellation notifications
to be bidirectional - that is, when you subscribe to completion
notifications on a Future, you can also subscribe to cancellation
notifications. Then it's possible to cancel a given future without breaking
any other listeners
On Fri, Apr 19, 2013 at 2:24 PM, Ron Buckton wrote:
> My version of the PromiseResolver provides resolve/reject methods and does
> not include an ‘accept’ method. My understanding of this is that
> FutureResolver#accept resolves the value explicitly, while
> FutureResolver#resolve hooks the Future
I’ll preface this with a disclaimer that I’m not directly involved with any of
the standards discussions, TypeScript, or IE at Microsoft, but rather am
expressing my interest as a producer and consumer of Promises/Futures while
building cloud applications. I’ve published a few variations of Prom
Histograms are looking like a good collection of examples for experimenting
with ParallelJS
Here are some histogram options
1) dense histograms where some bins have a zero entry and
2) sparse histograms where only the non-zero bins are stored
Sometimes you know the number of bins b
Hi Ron,
Comments inline.
On Wed, Apr 17, 2013 at 7:35 PM, Ron Buckton wrote:
> As someone who has been interested in Promises/Futures in JavaScript for a
> number of years, I'd like to throw in my $0.02 regarding a proposed API for
> Promises/Futures for thoughts:
>
> https://gist.github.com/rbu
12 matches
Mail list logo
