Is not clear how to hookup Django's URL routing to the channel routing, or if it even possible? about channels

[andrewgodwin]

(Generally, you don't want to route http.request in the routing and just leave it out so it does the default, which is exactly what you want. You only need to route it yourself if you're doing something unusually low-level)

[andrewgodwin]

Good point, I thought I had. Added a paragraph in there.

[carltongibson]

@itsmehdi97 Take a look at the example here: https://channels.readthedocs.io/en/stable/topics/routing.html#urlrouter
It covers the exact use-case you're asking about.

[andrewgodwin]

Yes, you can use the channels.handler.ViewConsumer to pass any http.request message into the view system, though this is done for you by default.

In addition, in the latest master code, the routing gains the ability to route to custom HTTP endpoints/WebSocket consumers based on url (path), and will always fall back to Django's view handling if nothing processes a http.request message.

[mandx]

Got it, thanks! I just didn't find the docs section stating that this already happens by default. Thanks for the quick reply!

[ThaJay]

Channels is looking really good this far. Perhaps explicitly add this to the starting section of the docs? I did not find it either so had to come here to find this out.

[itsmehdi97]

Is it possible to process some of http requests by channels consumers and some of them by the traditional django views based on their url?
Actually I need to add a single endpoint that should be asynchronous - using consumers - and others are simple rest-framework views.
I thought this issue is related to my question but I couldn't find the channels.handler.ViewConsumer you mentioned here .