Re: Websockets... again

2014-10-30 Thread Justin Holmes
Luis, I think what Alex and Aymeric are saying is that "websockets" (I use quotes to show that I mean not only the material outlined in RFC 6455 but also the general process of handling bytes-on-the-wire when 'pushing' data to the 'client') are ideally not part of the problem that Django (and WSGI

Re: Websockets... again

2014-10-29 Thread Alex Gaynor
And after you throw away the ORM, you have to throw away every other library that does blocking IO (anything in the stdlib, memcached, redis, requests, etc.). There are absolutely no affordances in WSGI for use with non-blocking libraries like asyncio or Twisted. Alex On Wed Oct 29 2014 at 1:45:5

Re: Websockets... again

2014-10-29 Thread Collin Anderson
Hi Luis, There is some work on making a WSGI2 that would include support for http/2 and likely websockets too. That would likely need to happen first or at the same time. https://github.com/python-web-sig/wsgi-ng You could also check out a project called "hendrix" which supports using websocke

Re: Websockets... again

2014-10-29 Thread Aymeric Augustin
Then the first step is to throw away the ORM. See my talk at DjangoCon US 2013 for details. -- Aymeric. > Le 28 oct. 2014 à 23:36, Marco Paolini a écrit : > > What if we do it with asyncio? > > 2014-10-28 22:47 GMT+01:00 Aymeric Augustin > : >> No, there isn’t. >> >> I assume that “includi

Re: Websockets... again

2014-10-29 Thread Florian Apolloner
On Tuesday, October 28, 2014 11:37:15 PM UTC+1, mpaolini wrote: > > What if we do it with asyncio? > It is 3.4 only, WSGI still has no support for Websockets and the API would change drastically… -- You received this message because you are subscribed to the Google Groups "Django developers

Re: Websockets... again

2014-10-28 Thread Marco Paolini
What if we do it with asyncio? 2014-10-28 22:47 GMT+01:00 Aymeric Augustin < aymeric.augus...@polytechnique.org>: > No, there isn’t. > > I assume that “including in core” means at least “making usable in > combination with WSGI and with the ORM”. > > Even if we disregard for a minute the fact tha

Re: Websockets... again

2014-10-28 Thread Aymeric Augustin
No, there isn’t. I assume that “including in core” means at least “making usable in combination with WSGI and with the ORM”. Even if we disregard for a minute the fact that WSGI is incompatible with websockets, the ORM is a hard problem, because current solutions involve either (a) threads — n