Hi! This is really awesome news! Can I suggest to use WebRTC data channel instead of Websockets?
I think we should make a paradigm shift and move to use WebRTC instead of Websockets. This allows many interesting properties: * connections can be based on SCTP * have multi-path routing * you can have data packets which are reliable or unreliable * you can even have backpressure support (imagine that you could push back on Meteor publish because client cannot handle observes as quickly as server is pushing) There is a great open source project already available which provides both client server suppor: https://github.com/feross/simple-peer Some interesting links to read: * https://github.com/webrtcftw/goals/issues/1 * https://github.com/jbenet/random-ideas/issues/13 I opened a ticket as well: https://github.com/andrewgodwin/channels/issues/38 Mitar On Fri, Dec 11, 2015 at 10:18 AM, Andrew Godwin <[email protected]> wrote: > Hi everyone, > > For those who haven't seen, Mozilla has awarded $150,000 to Django for work > on Channels and request/response improvements lifted from REST Framework. > More in the blog post here: > https://www.djangoproject.com/weblog/2015/dec/11/django-awarded-moss-grant/ > > I'll be coordinating this effort for the most part, but we're still working > out who to fund and the roadmap for the project, as well as work out how we > can pay people for their work on a different scale to the Django Fellowship, > so it might take a bit of time! > > I'll be back on here with some questions for people to discuss/answer about > the channels design at some point soon, but a lot of the basic design is > already up at http://channels.readthedocs.org, so take a read over that if > you're interested. > > What I can say is that my intention is to both bake Channels into the next > major release of Django, as well as hopefully release a pluggable app > version that will run on 1.8 and 1.9 - I have some plans around how to do > that effectively, but they involve hitherto unforged paths around Django and > how we package dependencies, so I can't say we'll get there 100%. > > Andrew > > -- > 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 http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAFwN1upjXf2LLk2gGA9mzdPQn4DbWehSHNFWhF-GkEk4q54gHA%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- 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/CAKLmikNtJhHQntNaSWvyeiz4qhVunM4OZ%2BJM-9v4VpuArmfsdQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
