Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jetty-users] Jetty PUSH strategy

Hi,

I looked inside the codes to find out the strategy of PUSH and got some problems.

When fetching a resource the client has 3 possibilities:
  • the resource is not being pushed
  • the resource is being pushed, but the data has not yet arrived
  • the resource is being pushed, and the data has started to arrive
What is the strategy used when facing case 2 "the resource is being pushed, but the data has not yet arrived"? 
Jetty sends request as follows:
session.syn(new SynInfo(headers, true), new StreamFrameListener.Adapter()...
So IMO there will be some check up in "syn()" to determine if the resource is being pushed, but I did not find related logic, so what is the mechanism in JETTY to solve case 2 in order to avoid sending redundant "GET"?


Back to the top