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.
