Hi, On Sun, Sep 27, 2015 at 7:12 PM, Muhui Jiang <[email protected]> wrote: > Hi > > But I find chrome will send window_update frame. Here is a part of the > packages when I made request to google.com > > t=13293813 [st= 0] HTTP2_STREAM_UPDATE_RECV_WINDOW > --> delta = 15663105 > --> window_size = 15728640 > t=13293813 [st= 0] HTTP2_SESSION_SENT_WINDOW_UPDATE_FRAME > --> delta = 15663105 > --> stream_id = 0 > t=13294034 [st= 221] HTTP2_SESSION_RECV_SETTINGS > --> clear_persisted = false > --> host = "www.google.com:443" > t=13294034 [st= 221] HTTP2_SESSION_RECV_SETTING > --> flags = 0 > --> id = 3 > --> value = 100 > t=13294034 [st= 221] HTTP2_SESSION_UPDATE_STREAMS_SEND_WINDOW_SIZE > --> delta_window_size = 983041 > > > You can see the client has send the window_update_frame. And when I set the > key 4(initial ) as 100. I find all the frames I received is 100. I was > wondering why the size of the frame I received is configured by the settings > frame? It seems I can do flow control by using settings frame. I am confused > why not using window_update frame, which is responsible for flow control.
I don't understand what you want to do. The client will send window updates whenever it deems needed, and typically this is subject to complex algorithms that may involve the bandwidth delay product (BDP), etc. You really don't want to mess with flow control. So, what is it that you want to do ? -- Simone Bordet ---- http://cometd.org http://webtide.com Developer advice, training, services and support from the Jetty & CometD experts. _______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
