Re: Multiple websocket connection vs single websocket connection when using django channels

Yes, I guess that's how to work around per connection for a user. Thank you for your input! On Fri, Apr 6, 2018 at 9:49 PM, Ken Whitesell wrote: > Hi Robin, > > I can't speak to any generalized situations, or what might be considered > "best practices" or most optimal. > > What I can say is that

Re: Multiple websocket connection vs single websocket connection when using django channels

Hi Robin, I can't speak to any generalized situations, or what might be considered "best practices" or most optimal. What I can say is that we have gone with the single websocket connection for each client - whether it's a real person at a browser or an application. All our communications thro

Multiple websocket connection vs single websocket connection when using django channels

I’m looking into creating an app that may utilize chat and notifications as well. I’m interested in what others have to say about this as well -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving ema

Multiple websocket connection vs single websocket connection when using django channels

Hi, Suppose an application has features like Chat, Notification and Activity feeds. I would like to know whether its recommended to have different websocket connection for different feautues for each user. Meaning for chat purpose a separate socket connection, for notification another separate