One connection per request? #4

Open
fengsp opened this Issue Nov 16, 2013 · 3 comments

Comments

Projects
None yet
4 participants

fengsp commented Nov 16, 2013

I have noticed that flask-rq does not use context-locals to save the redis connection, which means that everytime one request comes in, we are having a new connection.

What I need here is one connection manager so I do not have to handle connections myself.

Any reasons? So flask-rq is just a config manager? I do not see anything else meaningful here.

malthe commented Aug 14, 2014

Indeed. This extension is not meaningful at all. I was about to submit a pull request that removes the custom connection behavior, but then realized that with that removed, there's virtually no code left.

Collaborator

joostdevries commented May 29, 2015

@fengsp @malthe I agree with you that using an app context would make sense. I plan to get some work done on this the coming days/weeks. Out of curiosity: are you using flask-script?

Any news?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment