7 Commits

Author	SHA1	Message	Date
Ashesh Vashi	61698b7b4d	Do not use the sqlite for session handling, as the old implementation is ... optimized to work from multiple threads. It has too many frequent transaction from multiple threads, and that tends to result into the 'database is locked' error of sqlite. With the new implemenation, we're using the caching mechanism, which keep the data in the memory all the time, and saves it on request completion, and loads it only for the first time. Also, it will storage the data using pickle, which will be faster than accessing sqlite. Fixes #1329	2016-07-08 16:57:46 +05:30
Dave Page	7d0fe669ca	Code tidy.	2016-06-21 14:21:06 +01:00
Dave Page	3026b470e9	Optimise Python imports.	2016-06-21 14:12:14 +01:00
Ashesh Vashi	e8b4bb909b	Do not honour the session-id, longer than 40 characters, instead create ... new session-id in that case.	2016-05-09 00:04:37 +05:30
Khushboo Vashi	970e0c3540	[Python 3] Fixed an issue iterate the keys from the session loaded from ... the sqlite.	2016-04-26 16:16:29 +05:30
Murtuza Zabuawala	12a0cb1ba1	[Python 3] Fixed the issue loading the value for the session key from the sqlite.	2016-03-23 12:40:11 +05:30
Ashesh Vashi	3c366fafe7	Server side session management support.	2016-03-22 15:05:43 +00:00