On Thursday, May 5, 2016, Andrew Godwin <and...@aeracode.org> wrote: > > Do you have a link to the presentation about them removing it? >
https://youtu.be/839rskyJaro around 34 minutes and onwards, another version is https://youtu.be/2dG5HeM7MvA at 24 minutes. They were tackling a bit different problem, so their lessons might not apply. Most importantly they weren't aiming for websockets at all, just for high availability and throughput for normal HTTP traffic. On the other hand, the architecture of broxy itself is pretty much the same as Daphne, and they felt they had problems with it. The way we have approached recent feature additions is that we let them prove themselves outside of core. I think the crucial question is why Channels can't do this, that is why can't we wait some time and let actual production deployments prove the design? I know South is an example of why some features have a hard time living outside core. But DRF is an example that a feature crucial to modern web development can work very well outside of core. - Anssi -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/CALMtK1FDXaa2kMAo69NO7ji-Cpd4sdTwDWgaysx9NRGH%2BGH%2BSw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
