5 at 23:40, BearXu wrote:
> Sorry, I haven't read the source code. But I basically read the doc. Thus
> in a multithreaded env, we will use Redis or something to implement the one
> to one chat function, am I right?
>
> Thus people might be confused with the different channels'
or Worker processes in memory
> mode will just fail.
>
> Andrew
>
> On Tue, Jun 16, 2015 at 12:48 AM, BearXu wrote:
>
>> Personally I don't agree with implementing the Channel using in-memory
>> mode first. Writing code to communicate among sockets will becom
Personally I don't agree with implementing the Channel using in-memory mode
first. Writing code to communicate among sockets will become very
difficult for me(ordinary developer). If we see async in Django as a tool
instead of a coding style, I think Redis/NoSql/Database backend/ is good
enough as
