Sounds interesting. Not sure I have any particular suggestions, but can add some context around the plans I had. (Possibly still *have* , at a later date.)
My rough plan for Websockets support is a little similar, in that it'd be able easy ways to mirror an existing HTTP endpoint with an equivalent WS endpoint that provides streaming updates whenever the content changes. Personally I was planning to approach it as a separate proxy service, and use Redis Pub/Sub for the webapp to notify the Websocket server whenever there are changes. An approach that works entirely in Django would be great tho. Separate issue this, but I think the biggest thing missing for folks ATM is probably just a lack of tutorials or blog posts on using Channels and REST framework together. - T. -- You received this message because you are subscribed to the Google Groups "Django REST framework" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
