Upcoming SPDY support details
alek.storm at gmail.com
Thu May 17 13:52:30 UTC 2012
That's perfectly reasonable. Thanks for the quick and clear answers. Is
there somewhere online the in-progress SPDY implementation has been posted?
If not, what's the current estimated date of release?
On Thu, May 17, 2012 at 8:17 AM, Valentin V. Bartenev <ne at vbart.ru> wrote:
> On Thursday 17 May 2012 16:06:21 Alek Storm wrote:
> > On Thu, May 17, 2012 at 6:23 AM, Valentin V. Bartenev <ne at vbart.ru>
> > > First implementation of SPDY support will work only on frontend side.
> > > nginx
> > > will be able to talk with backends by HTTP, FastCGI, uwsgi, or SCGI
> > > protocols.
> > Got it. Looking forward to backend SPDY support, so crucial advantages
> > multiplexing are preserved. Will nginx at least add headers like
> > "X-Priority" to the forwarded request?
> Surely, I added the $spdy_request_priority configuration variable and it is
> suitable for such tasks.
> > > that
> > > the next step is to add pushing by special response header from backend
> > > (like
> > > "X-Accel-Redirect" but with the list of URIs to push).
> > That'll work, but am I correct in assuming that the response containing
> > "X-Accel-Redirect" is different from the response to the original
> In the most simplest implementation they will be the same.
> > If they are the same, then nginx will not be notified of the URIs to push
> > until the server is ready to send the headers for the response to the
> > original request. This would be more restrictive than SPDY's semantics,
> > which allow pushing resources before the SYN_REPLY frame for the original
> > request is even sent.
> Yes, you're right. And this question is still undecided and requires
> investigation. I think that we also need some sort of configuration
> for server pushing.
> wbr, Valentin V. Bartenev
> nginx-devel mailing list
> nginx-devel at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx-devel