Added Redis Stream backend.

[hramezani]

No description provided.

[hramezani]

Here I want to wait for at least one stream.
Don't know is it a good approach or not?

[woile]

Doesn't it work fine without the sleep? It should only stop reading if timeout is specified. I'll check it tomorrow

[lovelydinosaur]

Actually, it's a bit complicated. For instance, we also want to properly cover the case where a new stream is subscribed too, while we're waiting on an existing xread.

[lovelydinosaur]

Fantastic stuff! Therre's a bit of complexity around how we'll deal with waiting for/issuing/canceling the xread that'll need a bit of thinking over.

I'm wondering if a good precursor to this PR would be to first just implement an aioredis based PUB/SUB implementation. That looks to be more maintained that our existing dependency of asyncio-redis, and since it supports the stream API that asyncio-redis doesn't, it'd be a better default for us.

[hramezani]

Sorry I have closed the PR by mistake.
@tomchristie Do you mean to change the current redis backend and use aioredis instead of asyncio-redis? if so, I can take care of it.

[lovelydinosaur]

Do you mean to change the current redis backend and use aioredis instead of asyncio-redis? if so, I can take care of it.

Yup.

(I actually meant adding an aioredis PUB/SUB implementation in addition to the existing asyncio-redis PUB/SUB one, but actually let's just change it over competely, as the simpler option.)

[lostb1t]

Im very interested in this backend. Is there a way to push this forward without forking?

[carltongibson]

@sarendsen Using your own fork and reporting any issues is a good way forward.