Hi,
We're currently working on a server application using Django as framework.
Now, some advanced use cases appeared on the horizon, and we're evaluating how we'll be able to solve them in the future.
We came across https://blog.heroku.com/in_deep_with_django_channels_the_future_of_real_time_apps_in_django which advises to use "Django Channels" for that.
The linked article claims that "The plan is to roll Channels into Django for the 1.10 release" - but as far as I can see, it's not in 1.10 nor 1.11. Can anyone confirm my findings?
Additionally, the linked article shows "background processes", which could fit nicely into our concept, as we need functionalities like:
- Some pool with state information about certain clients (whether they're currently connected via web socket, which messages they sent etc...)
- Based on some timers (scheduled jobs, or clients were not connecting for some time, etc...) we need to get active on the server side (e. G. send emails, or send messages via web socket to other clients, etc...)
Can those background processes be used to implement such functionality? We did not find any documentation about them apart from the image yet, so pointers are welcome. :-)
The pool information mentioned above needs also be available for clients using http messages, so we'll need to access that data from the "view functions".
Is it possible and feasible to implement those features using Django?
Thanks in advance,
Markus Schaber
-- We're currently working on a server application using Django as framework.
Now, some advanced use cases appeared on the horizon, and we're evaluating how we'll be able to solve them in the future.
We came across https://blog.heroku.com/in_deep_with_django_channels_the_future_of_real_time_apps_in_django which advises to use "Django Channels" for that.
The linked article claims that "The plan is to roll Channels into Django for the 1.10 release" - but as far as I can see, it's not in 1.10 nor 1.11. Can anyone confirm my findings?
Additionally, the linked article shows "background processes", which could fit nicely into our concept, as we need functionalities like:
- Some pool with state information about certain clients (whether they're currently connected via web socket, which messages they sent etc...)
- Based on some timers (scheduled jobs, or clients were not connecting for some time, etc...) we need to get active on the server side (e. G. send emails, or send messages via web socket to other clients, etc...)
Can those background processes be used to implement such functionality? We did not find any documentation about them apart from the image yet, so pointers are welcome. :-)
The pool information mentioned above needs also be available for clients using http messages, so we'll need to access that data from the "view functions".
Is it possible and feasible to implement those features using Django?
Thanks in advance,
Markus Schaber
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/3eb9e492-c7bf-472e-81dd-5957df8ed3bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment