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

--===============1095296656863892126==
Content-Type: multipart/alternative; boundary=001a11401a902a29e60528a6fef1

--001a11401a902a29e60528a6fef1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 6, 2016 at 10:19 AM Aymeric Augustin <
aymeric.augustin-o/5/jSaJEHk+NdeTPqioyti2O/[email protected]> wrote:

> Hello Beno=C3=AEt,
>
> Thanks for clarifying that you also had the reverse problem in mind,
> headers sent by applications. This side is less problematic in the sense
> that application authors can adapt to stronger requirements.
>
> In general this is a bit of a mess due to differences between what the RF=
C
> 2616 says and what browsers do in practice. That=E2=80=99s why I believe =
the
> pragmatic solution is to exchange bytes. (This isn=E2=80=99t a major issu=
e in the
> grand scheme of things anyway.)
>
> Best regards,
>
> --
> Aymeric.
>
>
Since sockets are only accepting bytes in python 3.x,  having everything as
bytes would also allow the server to process the response more easily...


- beno=C3=AEt

--001a11401a902a29e60528a6fef1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed=
, Jan 6, 2016 at 10:19 AM Aymeric Augustin &lt;<a href=3D"mailto:aymeric.au=
gustin-o/5/jSaJEHk+NdeTPqioyti2O/[email protected]">aymeric.augustin-o/5/jSaJEHk+NdeTPqioyti2O/[email protected]</a>&gt; wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word=
">Hello Beno=C3=AEt,<div><br></div><div>Thanks for clarifying that you also=
 had the reverse problem in mind, headers sent by applications. This side i=
s less problematic in the sense that application authors can adapt to stron=
ger requirements.</div><div><br></div><div>In general this is a bit of a me=
ss due to differences between what the RFC 2616 says and what browsers do i=
n practice. That=E2=80=99s why I believe the pragmatic solution is to excha=
nge bytes. (This isn=E2=80=99t a major issue in the grand scheme of things =
anyway.)</div><div><br></div><div>Best regards,</div><div><br></div><div></=
div></div><div style=3D"word-wrap:break-word"><div><div>
<div>--=C2=A0</div><div>Aymeric.</div>

</div></div></div><div style=3D"word-wrap:break-word"><div>
<br><div><blockquote type=3D"cite"><div></div></blockquote></div></div></di=
v></blockquote><div><br></div><div><span><div style=3D"font-size:13px">Sinc=
e sockets are only accepting bytes in python 3.x, =C2=A0having everything a=
s bytes would also allow the server to process the response more easily...<=
/div><div style=3D"font-size:13px"><br></div><div style=3D"font-size:13px">=
<br></div><div style=3D"font-size:13px">- beno=C3=AEt</div></span></div></d=
iv></div>

--001a11401a902a29e60528a6fef1--

--===============1095296656863892126==
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

--===============1095296656863892126==--