prioritization
techniques in its Google Maps application, internally to the Google Chrome
browser, and also as a part of the SPDY protocol.
On Sun, Apr 18, 2010 at 10:37 PM, Anne van Kesteren wrote:
> On Fri, 16 Apr 2010 18:03:08 +0900, Mike Belshe
> wrote:
>
>> On Fri, Ap
Correct. Sorry.
Here is an updated doc:
https://docs.google.com/a/google.com/document/pub?id=1TcKtHi-XUVKXj9erQkkBXdidnG78lhK04D-2lh4O51Y
Mike
On Thu, Jun 3, 2010 at 2:11 AM, timeless wrote:
> On Wed, Jun 2, 2010 at 10:11 PM, Mike Belshe wrote:
> > Changes:
> >* changed
On Tue, Aug 3, 2010 at 5:45 AM, Anne van Kesteren wrote:
> On Thu, 03 Jun 2010 17:37:05 +0200, Mike Belshe
> wrote:
>
>> Here is an updated doc:
>>
>> https://docs.google.com/a/google.com/document/pub?id=1TcKtHi-XUVKXj9erQkkBXdidnG78lhK04D-2lh4O51Y
>>
>
&g
arted.
// Otherwise returns the difference between the stop and start times.
this.microseconds = function() {}
}
Thanks,
Mike
Mike Belshe
mbel...@google.com
Hi,
I'm a developer on the chrome team, and also working on SPDY.
Others here at Google have requested that we expose some of the
priority-based resource loading mechanics to applications so that
applications can hint to the browser more information about which resources
are critical and which ar
m not fussy about what priorities are exposed or what we call them - so
long as they are relatively few in number to avoid unnecessary complexity.
(e.g. 3-5 priority buckets seems fine)
Mike
>
>
> -Olli
>
>
>
> On 4/13/10 7:13 PM, Mike Belshe wrote:
>
>> Hi,
gt; https://build.mozilla.org/tryserver-builds/opet...@mozilla.com-xhr_priority/
>
>
>
> -Olli
>
>
> On 4/13/10 8:36 PM, Mike Belshe wrote:
>
>> On Tue, Apr 13, 2010 at 9:36 AM, Olli Pettay > <mailto:olli.pet...@helsinki.fi>> wrote:
>>
>>
On Thu, Apr 15, 2010 at 11:00 PM, Anne van Kesteren wrote:
> On Wed, 14 Apr 2010 01:13:46 +0900, Mike Belshe
> wrote:
>
>> // Set the load priority for this request.
>> void setPriority(unsigned short priority);
>>
>
> Any reason this is not an attribute named
On Fri, Apr 16, 2010 at 1:37 AM, Anne van Kesteren wrote:
> On Fri, 16 Apr 2010 17:30:04 +0900, Mike Belshe
> wrote:
>
>> On Thu, Apr 15, 2010 at 11:00 PM, Anne van Kesteren > >wrote:
>>
>>> Other than that I wonder if we should maybe simply use string values
