On Jul 10, 2006, at 2:37 PM, dmiller wrote: > This is a good argument to have users manage SessionContext > instances explicitly (for thread-local behavior) rather than having > it implicitly created behind the scenes. Maybe the threadlocal mod > should be deprecated and a new tutorial should be written up to > demonstrate how to get thread-local behavior using SessionContext? >
people *love* the threadlocal mod. i still get some flak for threadlocal no longer being the default behavior; the whole 0.2 change really pushes the limits for a lot of users who like the "old and easy" way of doing things (even though the "old" way only existed for like 3 months). at most, I would put the docs for sessioncontext ahead of threadlocals, suggesting it as a less magical way of doing things...but i wouldnt deprecate threadlocal. i think the solution is to just get the mapper to properly organize the extensions sent to it, and also get activemapper to use the threadlocal's objectstore if its already plugged in. this stuff is not that complicated. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
