Hi! On Sat, Dec 12, 2015 at 6:29 AM, Aymeric Augustin <[email protected]> wrote: > Unless I missed something, channels aren’t about websockets. They add > asynchronous processing capabilities to Django. They aim at being compatible > with any bidirectional protocol.
Yes, but currently, that "bidirectional protocol" is "bidirectional protocol without backpressure" which makes it really useless in any serious production use with scaling. It is interesting for smaller toy use cases, but without backpressure you simply cannot handle congestion and your systems blow in your user's face. node.js has learned this the hard way by reimplementing their streaming API multiple times. What I would propose is that Django officially exposes channels API with backpressure and then for simpler projects (or one where you do not care about delivery) one can use Websockets, but otherwise for production use for heavy loads WebRTC data channels with backpressure should be provided. > At this point, I’m not convinced that simple-peer is sufficiently mainstream > to be the recommended solution for Django websites. No, that is just an example of the node.js module which provides server-side WebRTC support. And yes, this is something which is cutting edge. I would be completely OK by supporting Websockets now on the transport level, but the API level should understand and support backpressure. Otherwise we will have issues in the future once this feature gets widely deployed and started using in production. Mitar -- http://mitar.tnode.com/ https://twitter.com/mitar_m -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAKLmikPjYgB3LUsSrDvxQ20rtopAU21meC6xNLRRjcx1y%3DY76Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
