Thanks for the reply. I didn't realize that ws4redis doesn't have the
concepts of consumers and routing. That's something I'll have to look into
further. The documentation for ws4redis isn't great so that makes it
harder.
On Saturday, August 5, 2017 at 9:19:24 AM UTC-4, Artem Malyshev wrote:
>
Hi,
I look at django-websockets-redis really quickly. If you decide to use
Redis ASGI layer it may look familiar.
Main differences I notice so far:
- ws4redis doesn't have concept of consumers and routing
- it's coupled to the subset of WebSocket usage
- it's propagate redis to the library api
Hi, thanks for feedback!
I need some time to dig into django-websocket-redis. I'll come back to you soon.
Regards, Artem.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an
I'm trying to evaluate these two Websockets solutions for Django. Has
anyone here done compared these?
I don't fully understand what the differences between them are. I think the
main difference is that Channels can generalize all requests (websocket or
request/response) to be handled by channe
4 matches
Mail list logo