Thanks for that! I've never tested it in a multi-threaded environment.
On Sat, Feb 11, 2012 at 4:41 AM, nick name <i.like.privacy....@gmail.com>wrote: > This solution will lead to a race condition. Do not use it! > > If you have multiple threads, they might update your commons at the same > time and you'll get request from one session, and session from another, and > db from a third. > > "current" is a thread-local thing, guaranteed not to be touched by any > other part - use "current", not "common" (or whatever your own module is > called) > -- Sathvik Ponangi
