One architecture you could consider, is to put all the sensor values into redis or similar. Have a worker to out the values into redis from the automation source.
-- Then use each websocket recieve event to add the reply channel to the group which gets the appropriate sensor value.
You will probably need a second worker to forward redis messages to the appropriate group.
But you can end up with the the values going down a couple of channels, and each user doesn't need a separate worker.
Personally I'd do as much of be the filtering on the client side as possible, if there is no security concern with publishing the values to a user send the values to them. The client side code can ignore it if necessary.
On 13 Oct 2017 07:14, "'matrix1900' via Django users" <django-users@googlegroups.com> wrote:
Hi Andrew,thanks for the answer.Are there some Examples available for using Background Worker and receive/send websockets in there ?I am not sure, if it is the better way to use celery or should I use the background worker?My Project:I should develop a maintain website for a automation control. Each user can view different sensor values (Described on several websites) from the automation control.IDEA: Each user have his own background worker which request the sensor values from the automation control and send the information to the user. The sensor values are updated upon change. (Providing Live DATA)
Am Donnerstag, 12. Oktober 2017 20:05:42 UTC+2 schrieb Andrew Godwin:On Wed, Oct 11, 2017 at 3:02 AM, 'matrix1900' via Django users <django...@googlegroups.com> wrote:Hi together,I try to get started with Django Channels. I have actually two questions:1. I use web sockets with channels. I want to have for each frontend user which opens the website his own websocket channel without groups. I am not sure how does it works when several Users opens the website ? Has each frontend user his own consumer thread which handles the web socket messages ? How are the concept here?The server holds on to all the websockets in one big async thread, then calls your Django code synchronously whenever an event happens on the socket.2. How can I receive websocket messages in a separate task. I found in the FAQ on the Channels Site the hint to use receive_many() but I'm not sure how to use it exactly.You shouldn't do this, use the normal worker pattern, there's lot more than just receive_many to do3. How can I start a separate task in the consumer.py after receive a message ('websocket.receive')( for example: In Consumer I get a message via websocket from the frontend user, according to the message I start a process with some arguments, after execute the process, I get the results back and send it to the individual websocket channel client)You have to send it to a custom channel with the reply_channel of the socket, have a worker listen on that channel, and when it is done send information back to the reply_channel.Andrew--To view this discussion on the web visit https://groups.google.com/d/
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 .msgid/django-users/7ebb5b85- .064b-421f-a906-a638ba97bb10% 40googlegroups.com
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/CA%2B_0JkLtGUd49FNoAt6jBZeNp7%2Bj7PPOh2UF%3DogOAWBxg_CjwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment