jiangmuhui at gmail.com
Tue Oct 13 15:20:47 UTC 2015
Thank you very much. Valentin
2015-10-13 23:16 GMT+08:00 Valentin V. Bartenev <vbart at nginx.com>:
> On Tuesday 13 October 2015 22:43:48 Muhui Jiang wrote:
> > Hi
> > Thank you so much. Valentin.
> > My understanding:
> > Though clinklittle128.png has higher priority, the server wants to send
> > first to the client. But because of flow control, the clinklittle128.png
> > blocked(waiting for the window update frame). But at this time the server
> > don't want to waste the resource, so it will send the index.html,
> > preloadjs.min.js etc. When the server received the window update frame,
> > it will send the clinklittle128.png once again. Am I right?
> Yes, that's right.
> > BTW: could you please locate the related source code for me. I want to
> > a deep research on it. Many Thanks
> The code related to exhausting flow control window is here:
> Here is what happens on receiving window update:
> wbr, Valentin V. Bartenev
> nginx mailing list
> nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx