W3C home > Mailing lists > Public > public-web-perf@w3.org > February 2014

Re: [Navigation Error Logging] Use promises instead of callbacks?

From: Arvind Jain <arvind@google.com>
Date: Wed, 12 Feb 2014 15:20:53 -0800
Message-ID: <CAOYaDdM++nVYUYH6o8s59sPiQdsLKSdGHa6NQvc9nZ0r2ajtdw@mail.gmail.com>
To: Jake Archibald <jakearchibald@chromium.org>
Cc: ttuttle <ttuttle@chromium.org>, public-web-perf <public-web-perf@w3.org>, Domenic Denicola <domenic@domenicdenicola.com>
OK Done.  Please check:
https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationErrorLogging/Overview.html


On Tue, Feb 11, 2014 at 2:24 AM, Jake Archibald
<jakearchibald@chromium.org>wrote:

> +1
>
> Any async success (and optionally, failure) API should use promises.
>
>
> On Tue, Feb 11, 2014 at 6:40 AM, Arvind Jain <arvind@google.com> wrote:
>
>> Does anyone else have an opinion? Should I go ahead and change
>> getNavigationErrors to return a promise?
>>
>> https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationErrorLogging/Overview.html
>>
>>
>> On Tue, Feb 4, 2014 at 2:35 PM, ttuttle <ttuttle@chromium.org> wrote:
>>
>>> Hi,
>>>
>>> At Domenic Denicola's suggestion, can we have getNavigationErrors
>>> return a promise instead of a callback?  It should fail if the site
>>> has never registered for error logging.
>>>
>>> Thanks,
>>>
>>> ttuttle
>>>
>>
>>
>
Received on Wednesday, 12 February 2014 23:21:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:38 UTC