+1 on this! Let me know if you have figured it out Steve. I have also long time spent on "Reading Push" while investigating different server push scenarios. And in fact it seems like the resource is still on the server while "Reading Push". I've implemented server push with node-spdy and in my case, the pushed stream is not finished on the server, i.e still "Reading Push" on the client, until the client is done "Reading Push". I've read that the pushed resource should be available from the browsers memory (not the cache), but this is not the case for my scenarios since the stream is still on the server.
Den lördag 31 december 2016 kl. 06:58:47 UTC+1 skrev steve manuel: > > I know this is a Chrome thing, but my questions pertain more to what the > server has actually sent prior to the "pushed" response seen in the > screenshot below. > > > > <https://lh3.googleusercontent.com/-luQ6SIjo8lg/WGa2ZrRkKzI/AAAAAAAAAAM/ChThg6BIRAcYeXt_ALmTR9VwANpqWMf0gCLcB/s1600/push-ponzu.png> > > [click to enlarge] > <https://lh3.googleusercontent.com/-luQ6SIjo8lg/WGa2ZrRkKzI/AAAAAAAAAAM/ChThg6BIRAcYeXt_ALmTR9VwANpqWMf0gCLcB/s1600/push-ponzu.png> > > can anyone explain what is happening in the 0.53ms spent 'Reading Push'? > The json response was server pushed in a prior response. furthermore, does > it matter that the push was executed after the initial response was > written? i can't tell from tests. > > from http2 spec, it seems like PUSH_PROMISE frames aren't read until > receiver accepts the response. Is 'Reading Push' time spent accepting > response (and then receiving pushed data from stream)? > > I have some concerns about overloading a client peer with pushed data. > there is a routine in my program which could potentially push hundreds of > resources - and I don't want to waste bandwidth or cause trouble for peers. > If the PUSH_PROMISE is all that is sent in a server push, and then data is > received only once the subsequent request is made then I'm probably fine. > > Just looking for some clarity on how a server implementation like Go's > handles this. I'm using the http.Pusher Push method in go1.8beta2 > > Thank you, > Steve > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
