Re: [whatwg] Array as first argument to fetch()

2015-03-27 Thread Anne van Kesteren
On Fri, Mar 27, 2015 at 1:50 PM, Brett Zamir wrote: > Thanks, I realize it's doable that way, but I think it makes for less > distracting code when the implementation details of the map call and such > are avoided for something as basic as loading resources... Write a function that abstracts it..

Re: [whatwg] Array as first argument to fetch()

2015-03-27 Thread Brett Zamir
On 3/27/2015 8:39 PM, Anne van Kesteren wrote: On Fri, Mar 27, 2015 at 1:28 PM, Brett Zamir wrote: Since fetch() is making life easier as is and in the spirit of promises, how about taking it a step further to simplify the frequent use case of needing to retrieve multiple resources and waiting

Re: [whatwg] Array as first argument to fetch()

2015-03-27 Thread Anne van Kesteren
On Fri, Mar 27, 2015 at 1:28 PM, Brett Zamir wrote: > Since fetch() is making life easier as is and in the spirit of promises, how > about taking it a step further to simplify the frequent use case of needing > to retrieve multiple resources and waiting for all to return? > > If the first argument

[whatwg] Array as first argument to fetch()

2015-03-27 Thread Brett Zamir
Since fetch() is making life easier as is and in the spirit of promises, how about taking it a step further to simplify the frequent use case of needing to retrieve multiple resources and waiting for all to return? If the first argument to fetch() could be an array, then fetch() could be made