Add support for sessions

[alculquicondor]

This will enable to reuse connections

[rburhum]

OK, careful with this. Sessions are tricky because postgres logging can be a performance bottleneck if this is not done carefully...

[alculquicondor]

Http sessions?

On Fri, Feb 19, 2016, 4:09 PM Ragi Yaser Burhum notifications@github.com
wrote:

OK, careful with this. Sessions are tricky because postgres logging can be
a performance bottleneck if this is not done carefully...

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

[rburhum]

I meant db sessions. Http sessions are actually even worse, because you cannot load balance web front-end. You are creating stateful connections for things that should be stateless by design.

All I am saying is to be careful by this. Think about this: If I separate the web tiers and put multiple machines to run the django process, will this make it even more difficult to have a load balancer in the front?

If the answer is 'no', then it makes sense. If the answer is 'yes', then there are all kinds of scalability issues we can run into with stateful http connections (i.e. what happens if the process is locked doing something like returning calls - do I just block all other requests since they will all be redirected to the same process?).