On Thursday, March 17, 2016 at 9:56:40 PM UTC+1, Jacob Kaplan-Moss wrote: > > I'd considered an API like this, and it's certainly clean and > straightforward. However, we've already got a URL routing library in > Django, so I think I'd like to try to find a way to re-use it for > websockets. It'd be a shame to have two different URL-routing-things in > Django (especially since they'd almost certainly have subtlety different > semantics). >
Absolutely, in my head I was thinking of putting url around those, or just refering to a URLConf (probably overkill), but I then opted for the most straight forward example. We should strive for the simplicity the current approach (in channels as of today) provides without making it too hard to decouple and split the handlers if needed. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/b8b8a2dd-c3b9-4a32-bd5b-1fc85cdba2b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
