Re: WSGI 2.0 Round 2: requirements and call for interest

--===============7685703305824742103==
Content-Type: multipart/signed; boundary="Apple-Mail=_3E43D623-6613-4DBF-A6A3-26D0F9764294"; protocol="application/pgp-signature"; micalg=pgp-sha256


--Apple-Mail=_3E43D623-6613-4DBF-A6A3-26D0F9764294
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 6 Jan 2016, at 09:48, Graham Dumpleton <[email protected]> =
wrote:
>=20
> If this does solve the push issue, what is there in HTTP/2 then that =
one couldn=E2=80=99t do via the existing WSGI interface?

Well, plenty, but none that we=E2=80=99d *want* to expose via WSGI with =
the possible exception of long-running bi-directional communications =
channels like Websockets, which you=E2=80=99ve already expressed a =
desire to expose in a different API. =3D)

Pushing via Link headers is not ideal because it delays the push until =
after the headers are ready to go, and there=E2=80=99s a tricky ordering =
concern here (RFC 7540 points out that any PUSH_PROMISE frames should be =
sent before the response headers and body are sent, which means that we =
temporarily block the response that is ready to go from WSGI. This is a =
minor concern, but worth noting.)

However, I=E2=80=99m happy to say that Pushing via Link headers is the =
way to go if we=E2=80=99d rather not specify a WSGI-specific API for it.

Cory


--Apple-Mail=_3E43D623-6613-4DBF-A6A3-26D0F9764294
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJWjPhLAAoJEHD+F/imQ+FbefEQANnykMg98uphjIVCBkbRSWGa
n2eV0P1FgPWpcAU4mJclaOpLVQdb+dJ+qc8IdTuMjHZ/GTejyvVTkWxHxyrFOTnz
AobaqViVB35hN0ZqH24NZ3QLfvnIt0hDRgbcefymWmy3QOceCHkQdHSYLid6F3RN
giX0q9r7sMXs3+lD9sScbkuKT89wn8i2pyXY2p4gFEbfHebvhxpxpVmAhm7viUrN
dAWjB9EL2Ixy58SQfIn5nszwEX0gIZVnNfW3NAq0coayw80W4FC/tf6QENzj48bq
Q+kox3c0JZTTgfGYM4uOnFXn4Nuh/puQrcdJ3uqt8AZRAvuVu+Fj2r8pe6/HjsiZ
H8RBD37iPGtU1Rw31Vvi0tkGPPg+YfcsWOZR4ndlBID6+2HXs1euu/x781sNbaLa
OXl7FpS1CYZL/1Nz4SBIujb7pQ2wKfrnyaNZvy2VYVNNyWBVfLEqO6z8mc7ghNZ3
xn4B8oxdb7RP4AA3zrrldCeTOhYe1b8Uf5pwKDVvHuMpUxhy+gLFlDpMgH1+jvwR
86xjvOn830TUGwBA2RTWb93qgLCA8lGyTvMCNmbtUiGX9q/Vme3QP/5n9OsG9ZIk
kGlNL26/EL3V2E29xrL3CxBxNN8bw6+mcbSTG70jaQjWV6nNFzMAb9DdMKBQb1xT
jQsznpjrrrAd79RnNWi4
=i2bc
-----END PGP SIGNATURE-----

--Apple-Mail=_3E43D623-6613-4DBF-A6A3-26D0F9764294--

--===============7685703305824742103==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Web-SIG mailing list
[email protected]
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe: https://mail.python.org/mailman/options/web-sig/gcpw-web-sig%40m.gmane.org

--===============7685703305824742103==--