Re: Django Websocket Implementation Request

['1337 Shadow Hacker' via Django developers (Contributions to Django itself)]

> They're not that popular actually, it seems...

They might become more popular, when they work behind proxies ... a limitation 
which you usually figure out after your first important client tries to connect 
from behind their corporate proxy, then you can implement polling again - a 
fallback that socket.io provides.

However, websockets are nice to have if you're using a Django library that 
supports data binding such as ryzom, maybe there are others but I'm not aware 
about them, and it doesn't implement the polling fallback so far afaik.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/STfktCMulCv9lYeEfdC96aFUmH4Y2_wz90LV9_15nmhqr0YCuThgrCJcZ32N3odKDtR0TThEBgxdxV_j-yjuZZNVHGwRE7bQ77mmiv0TVw8%3D%40protonmail.com.

Re: Django Websocket Implementation Request

[Confi Yobo]

Ok

On Sat, Aug 10, 2019 at 6:07 PM Carlton Gibson 
wrote:

>
> On 10 Aug 2019, at 18:51, Confi Yobo  wrote:
>
> So it should not be expected in 3.0? @ Carlton Gibson
>
>
> No. As per the previous comments, it’s not something likely to be included
> in core. Certainly not for 3.0.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/DF029827-57FD-4F88-8145-E5AB9A438355%40gmail.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAD9uRzc1GsR3Qs9JMv7AhvaCx-%3D2pbOYmwqTHhV9_a_XyeuE5g%40mail.gmail.com.

Re: Django Websocket Implementation Request

[Carlton Gibson]

> 
> On 10 Aug 2019, at 18:51, Confi Yobo  wrote:
> 
> So it should not be expected in 3.0? @ Carlton Gibson

No. As per the previous comments, it’s not something likely to be included in 
core. Certainly not for 3.0. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/DF029827-57FD-4F88-8145-E5AB9A438355%40gmail.com.

Re: Django Websocket Implementation Request

[Confi Yobo]

So it should not be expected in 3.0? @ Carlton Gibson

On Thursday, August 1, 2019 at 2:09:21 PM UTC+1, Confi Yobo wrote:
>
> 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 developers want to build an application that requires websocket they 
> use another web framework.
>
> So in my opinion and that of few other developers i'v  seen i think 
> websocket feature should be added to django out of the box(something like 
> socket.io would make a lot of sense).
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/c3480723-f659-4ab0-9ca6-6389834b2d0f%40googlegroups.com.

Re: Django Websocket Implementation Request

[Confi Yobo]

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 the Channels project is an
> official Django project, so it's as close as we can get so far. Future
> Django versions with async support will shrink Channels down significantly,
> and remove the need for it to be hosted differently, but the plan is still
> to have it as a separate package - we may write about it in the official
> docs, though.
>
> socket.io is even harder as it's fundamentally hard to scale - it needs
> stateful storage to aid in transferring connections, and this means it's
> really hard to have a single method that will work for everyone. Having
> "one right way to do it" is sort of a necessary prerequisite to having
> something in Django, and I just don't feel like it's there.
>
> Andrew
>
> On Fri, Aug 2, 2019 at 6:00 AM Confi Yobo  wrote:
>
>> 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 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 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 the Channel Layers bit... too but
 maybe that would/could be separate.) Hopefully this'll make it more focused
 and easier to follow

 But... I think websockets haven't turned out to be the One True Hammer
 people thought. (They're not that popular actually, it seems...) So I'm not
 sure we'd include support in core (vs keeping it in the third-party
 package.)

 I guess something to revisit after 3.0.

 Kind Regards,

 Carlton


 On Thursday, 1 August 2019 15:09:21 UTC+2, Confi Yobo wrote:
>
> 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 developers want to build an application that requires websocket they
> use another web framework.
>
> So in my opinion and that of few other developers i'v  seen i think
> websocket feature should be added to django out of the box(something like
> socket.io would make a lot of sense).
>
 --
 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 view this discussion on the web visit
 https://groups.google.com/d/msgid/django-developers/c561814d-941c-446f-8707-c2ef1ce8170e%40googlegroups.com
 
 .

>>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/CAD9uRzdwK6Luj9cKZN70FgRRRO%2BtrybZ16XwB-FjWiPXZu9Eqw%40mail.gmail.com
>> 
>> .
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAFwN1upE%2BikHmiserS%3DKKQsT_xu5wZO14jUaDUCqVXZ_43WZOQ%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this 

Re: Django Websocket Implementation Request

[Andrew Godwin]

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
versions with async support will shrink Channels down significantly, and
remove the need for it to be hosted differently, but the plan is still to
have it as a separate package - we may write about it in the official docs,
though.

socket.io is even harder as it's fundamentally hard to scale - it needs
stateful storage to aid in transferring connections, and this means it's
really hard to have a single method that will work for everyone. Having
"one right way to do it" is sort of a necessary prerequisite to having
something in Django, and I just don't feel like it's there.

Andrew

On Fri, Aug 2, 2019 at 6:00 AM Confi Yobo  wrote:

> 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 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 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 the Channel Layers bit... too but
>>> maybe that would/could be separate.) Hopefully this'll make it more focused
>>> and easier to follow
>>>
>>> But... I think websockets haven't turned out to be the One True Hammer
>>> people thought. (They're not that popular actually, it seems...) So I'm not
>>> sure we'd include support in core (vs keeping it in the third-party
>>> package.)
>>>
>>> I guess something to revisit after 3.0.
>>>
>>> Kind Regards,
>>>
>>> Carlton
>>>
>>>
>>> On Thursday, 1 August 2019 15:09:21 UTC+2, Confi Yobo wrote:

 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 developers want to build an application that requires websocket they
 use another web framework.

 So in my opinion and that of few other developers i'v  seen i think
 websocket feature should be added to django out of the box(something like
 socket.io would make a lot of sense).

>>> --
>>> 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 view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-developers/c561814d-941c-446f-8707-c2ef1ce8170e%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAD9uRzdwK6Luj9cKZN70FgRRRO%2BtrybZ16XwB-FjWiPXZu9Eqw%40mail.gmail.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAFwN1upE%2BikHmiserS%3DKKQsT_xu5wZO14jUaDUCqVXZ_43WZOQ%40mail.gmail.com.

Re: Django Websocket Implementation Request

[Confi Yobo]

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 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 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 the Channel Layers bit... too but maybe
>> that would/could be separate.) Hopefully this'll make it more focused and
>> easier to follow
>>
>> But... I think websockets haven't turned out to be the One True Hammer
>> people thought. (They're not that popular actually, it seems...) So I'm not
>> sure we'd include support in core (vs keeping it in the third-party
>> package.)
>>
>> I guess something to revisit after 3.0.
>>
>> Kind Regards,
>>
>> Carlton
>>
>>
>> On Thursday, 1 August 2019 15:09:21 UTC+2, Confi Yobo wrote:
>>>
>>> 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 developers want to build an application that requires websocket they
>>> use another web framework.
>>>
>>> So in my opinion and that of few other developers i'v  seen i think
>>> websocket feature should be added to django out of the box(something like
>>> socket.io would make a lot of sense).
>>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/c561814d-941c-446f-8707-c2ef1ce8170e%40googlegroups.com
>> 
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAD9uRzdwK6Luj9cKZN70FgRRRO%2BtrybZ16XwB-FjWiPXZu9Eqw%40mail.gmail.com.

Re: Django Websocket Implementation Request

[Confi Yobo]

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 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 the Channel Layers bit... too but maybe
> that would/could be separate.) Hopefully this'll make it more focused and
> easier to follow
>
> But... I think websockets haven't turned out to be the One True Hammer
> people thought. (They're not that popular actually, it seems...) So I'm not
> sure we'd include support in core (vs keeping it in the third-party
> package.)
>
> I guess something to revisit after 3.0.
>
> Kind Regards,
>
> Carlton
>
>
> On Thursday, 1 August 2019 15:09:21 UTC+2, Confi Yobo wrote:
>>
>> 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 developers want to build an application that requires websocket they
>> use another web framework.
>>
>> So in my opinion and that of few other developers i'v  seen i think
>> websocket feature should be added to django out of the box(something like
>> socket.io would make a lot of sense).
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/c561814d-941c-446f-8707-c2ef1ce8170e%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAD9uRzcpxHkhZ5hNUu1xF73nTF%3DpR_qmyV8nJweEvQmivz57KQ%40mail.gmail.com.

Re: Django Websocket Implementation Request

[Carlton Gibson]

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 the Channel Layers bit... too but maybe 
that would/could be separate.) Hopefully this'll make it more focused and 
easier to follow

But... I think websockets haven't turned out to be the One True Hammer 
people thought. (They're not that popular actually, it seems...) So I'm not 
sure we'd include support in core (vs keeping it in the third-party 
package.) 

I guess something to revisit after 3.0. 

Kind Regards,

Carlton


On Thursday, 1 August 2019 15:09:21 UTC+2, Confi Yobo wrote:
>
> 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 developers want to build an application that requires websocket they 
> use another web framework.
>
> So in my opinion and that of few other developers i'v  seen i think 
> websocket feature should be added to django out of the box(something like 
> socket.io would make a lot of sense).
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/c561814d-941c-446f-8707-c2ef1ce8170e%40googlegroups.com.

Django Websocket Implementation Request

[Confi Yobo]

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 developers want to build an application that requires websocket they
use another web framework.

So in my opinion and that of few other developers i'v  seen i think
websocket feature should be added to django out of the box(something like
socket.io would make a lot of sense).

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAD9uRzdHaQJdo3%2BBt%2BDzGfadvLTK%2B8gC7r2A75Q8a4L3dkN42Q%40mail.gmail.com.