The main reason to have a separate cookie is that the session filter is not necessarily enabled for all TurboGears applications. Therefore, I couldn't rely on the presence of the session cookie. 

In addition, storing identity information in the session isn't a particularly scalable solution because it diminishes the application's ability to scale across multiple machines. (Yes, I know CherryPy has file-based sessions and database sessions, but the performance of those aren't likely to exceed a direct database query.)

On 2 Dec, 2005, at 7:50 pm, p wrote:

I'm still not sure why you decided to create a separate cookie for

identity.


--

Jeff Watkins

http://newburyportion.com/


"Computers are like Old Testament gods; lots of rules and no mercy."

-- Joseph Campbell



Reply via email to