I've been monitoring this list for a bit, enough to see that 3.x is now
moving in the async direction.
Is there a roadmap as to where we want to get with this direction?
Or, to ask more directly:
I have been looking into django-channels for a while in order to start
catering for ever-increasing demands for more and more responsiveness in
my apps. Basically I see django-channels as a good approach at getting
the server to actually PUSH information to the clients. I sure hope I'm
not just wishful here, but that's how I understood this particular facet
of the project. There are some other things I also see quite appealing
in there.
Anyway, I understood that django-channels was a project just a tad too
big to simply be integrated into Django, but was heavily supported by
django core team?
OTOH I fear that with core django moving towards async will make
django-channels either hard to maintain or outright obsolete.
So, to finally arrive at the question: is the async action I have been
seeing going anywhere near where django-channels is today or is it a
completely separate effort? If the latter, what's the future outlook for
django-channels?
I sure hope I'm asking this in the right mailing list.
Thanks,
Jure
--
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/ceac365f-70a0-2b1f-de6a-9cb171df4a79%40gmail.com.
