Hi Andrew, Thanks for writing that up so comprehensively!
Definitely in favor of moving to a server:consumer interface - as you say that doesn't preclude over-the-network from being one of the possible deployment styles. I like your proposed approach to async vs sync variants of the interface. The callable returning a callable is a neat way around too, although I can't immediately figure out how eg. middleware looks against that pattern. Also does the interface look the same for worker:consumer? ie. Is it expected that `send()` could either be direct to server, or over a channel layer, with the client being agnostic as to which of those two cases will be used, or is the client expected to use the channel layer in that case? Cheers, T. :) -- 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/4c215111-c060-4ad6-af13-b177bf46c5b8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
