Hi, On Mon, Dec 30, 2013 at 9:55 AM, Ryan Young <[email protected]> wrote: > 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"?
I am not sure I understand whether you're talking server-side or client-side here. session.syn() is an API (usually) used by clients to send a request to the server, so it does not have any "push" code. The "push" code is on server side when replying to client requests. What are you trying to do ? -- Simone Bordet ---- http://cometd.org http://webtide.com http://intalio.com Developer advice, training, services and support from the Jetty & CometD experts. Intalio, the modern way to build business applications. _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
