Redis-likes for Session Storage?

[jaidetree]

This framework looks very impressive! I noticed in the docs the session backends include memory, cookies, or sql. Was curious if you'd be open to a PR that extends a redis (or redis-like) session store?

[aantron]

Could it be written as a library, which we could link to from the Dream repo/sites? The reason I am asking is because I am concerned about picking up a dependency, or else an awkward API with extra callbacks to bind it to a dependency dynamically. If there is any obstacle to writing a redis session backend as a library, I think we should fix that and I would be very open to a PR to that end.

[jaidetree]

I see, the memory, cookie, and db backends reuse resources already included in the framework whereas this would require at least a redis client library which may not get used by anything else. That said, it can be useful for async worker queues but understandably not a high priority.

A separate library with a link in the docs works for me as a staring point.

I'll start drafting that library. My plan was to match the other storage module APIs and use a popular\common redis client library so not expecting much chaos there, but will see how it goes.

If I do run into any barriers from the framework design I'll create issues to make sure it's something that needs to be addressed and to ensure we're on the same page for how to solve it.

[aantron]

Great, looking forward to that!