Re: Collating follow-up on the future of WSGI
Benoit Chesneau <[email protected]> Tue, 19 Jan 2016 21:43:02 +0000
| Newsgroups | gmane.comp.python.web |
|---|---|
| Message-ID | <CAJNb-9op83u9Zmk_9qtPY3H=3v_c66ZQMxh_Miz9_ohLgnr+Mw@mail.gmail.com> |
--===============6817218161457915916== Content-Type: multipart/alternative; boundary=001a114205ba977f860529b6c1dc --001a114205ba977f860529b6c1dc Content-Type: text/plain; charset=UTF-8 I will make a more complete answer soon. But about: > > Socket Escape Hatch > ~~~~~~~~~~~~~~~~~~~ > > Aside from Benoit, server operators were unanimously dismissive of the > idea of a socket 'escape hatch'. In general it seems like servers would not > be capable of achieving this. I think, therefore, this idea is unworkable. > > Well it does work. This is how websockets works in gunicorn. Escape is not the right term anyway. Think it as a socket *upgrade*. And then you would wonder why it would be unworkable. After all this is how SSL sockets works, so is the protocol negotiation in http2 ... There is nothing magic there until you try to over engineer the stuff. Upgrading a sockets means that you tell to the server to forget it. This is how most concurrent servers work today. - benoit --001a114205ba977f860529b6c1dc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">I will make a more complete answer soon. But about:<br><br= ><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"marg= in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br><br> Socket Escape Hatch<br> ~~~~~~~~~~~~~~~~~~~<br> <br> Aside from Benoit, server operators were unanimously dismissive of the idea= of a socket 'escape hatch'. In general it seems like servers would= not be capable of achieving this. I think, therefore, this idea is unworka= ble.<br><br></blockquote><div><br></div><div>Well it does work. This is how= websockets works in gunicorn.=C2=A0 Escape is not the right term anyway. T= hink it as a socket <b>upgrade</b>. And then you would wonder why it would = be unworkable. After all this is how SSL sockets works, so is the protocol = negotiation in http2 ...</div><div><br></div><div>There is nothing magic th= ere until you try to over engineer the stuff. Upgrading a sockets means tha= t you tell to the server to forget it. This is how most concurrent servers = work today.</div><div><br></div><div>- benoit</div></div></div> --001a114205ba977f860529b6c1dc-- --===============6817218161457915916== 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 --===============6817218161457915916==--