Some questions about Stream Priority in HTTP/2 -

Some questions about Stream Priority in HTTP/2 -

after reading http/2 specification, there curious stream priority.

in first paragraph @ "5.3.4 prioritization state management",

when stream removed dependency tree, dependencies can moved become dependent on parent of closed stream. weights of new dependencies recalculated distributing weight of dependency of closed stream proportionally based on weights of dependencies.

when parent stream closed, these paragraph describes dependencies's weights recalculated.

first question. without additional headers or priority frame, can stream's weight set headers or priority frame recalculated? weight mentioned these paragraph recalculated. word, weight mentioned these paragraph equal stream's weight set headers or priority frame.

in sec paragraph @ "5.3.4 prioritization state management"

streams removed dependency tree cause prioritization info lost. resources shared between streams same parent stream, means if stream in set closes or becomes blocked, spare capacity allocated stream distributed immediate neighbors of stream.

if "b" stream in closed or blocked state, spare capacity allocated "b" stream distributed other neighbors same parent. understand.

second question. https://cloud.githubusercontent.com/assets/1546031/6983712/2a91b88c-da5c-11e4-86dc-b02260be478f.png drawing first illustration in "5.3.4 prioritization state management". why "c" stream have 100 resources?

third question. https://cloud.githubusercontent.com/assets/1546031/6983961/d04d8984-da5e-11e4-8f61-6308e0e12d2b.png drawing sec illustration in "5.3.4 prioritization state management" equal starting weights. why "b" , "c" stream have 20 resources? because "d" stream block, think "b" , "c" stream have 30 resources

last question. "flow command window" related "stream priority"?

with sincere thanks

above question solved in http/2 spec github.

below links reply https://github.com/http2/http2-spec/issues/738

stream priority http2