Hi Pascal,
I know this is a very late reply, but there have been some things going
round my head that I thought I should get down.
*First,* some positive changes I think we can make from your suggestions:
1. I think in our release notes, for breaking changes that might need
some justificatio
Today the Django team issued 2.2.4, 2.1.11, and 1.11.23 as part of our security
process. These releases address security issues, and we encourage all users to
upgrade as soon as possible:
https://www.djangoproject.com/weblog/2019/aug/01/security-releases/
--
You received this message because y
This might be a little redundant as you would say but i see importance in
it.
Django should come chipped in with websocket implementation rather
developers using third party libraries like django-channels which are
difficult and most at times have poor documentation. I have seen many cases
where d
Hmmm. I guess Channel is doing more than just websockets, but I've always
thought it had good docs... Anyhow...
We'll see how the Async work goes, but a lot of channel will end up being
absorbed into Django itself. What, at this point, I guess that will leave
is "just" the websocket bit. (Maybe
Please consider it, cause the procedures of using third party websocket
library (mostly for production) is cumbersome
On Thu, Aug 1, 2019 at 2:22 PM Carlton Gibson
wrote:
> Hmmm. I guess Channel is doing more than just websockets, but I've always
> thought it had good docs... Anyhow...
>
> We'll
And socket.io kind of implementation is one thing developers from js like
us are missing in django.
On Thu, Aug 1, 2019 at 8:58 PM Confi Yobo wrote:
> Please consider it, cause the procedures of using third party websocket
> library (mostly for production) is cumbersome
>
> On Thu, Aug 1, 2019 a
Unfortunately, from my perspective, websocket support is tricky enough that
it's at least not on the short-term plan to bake into Django; it's used by
only a small fraction of our users, and the Channels project is an official
Django project, so it's as close as we can get so far. Future Django
ver
So it should not be expected in future release?
On Thu, Aug 1, 2019 at 9:14 PM Andrew Godwin wrote:
> Unfortunately, from my perspective, websocket support is tricky enough
> that it's at least not on the short-term plan to bake into Django; it's
> used by only a small fraction of our users, and
