On 8 Jan, 2006, at 2:02 pm, David Stanek wrote:
 What information exactly is being stored?

TG_Visit contains:

* Visit Key (40 character key used as cookie value)
* Create time
* Expiry (updated on each request)

What about sessions prevents them from being used in a clustered app?

Principally, sessions are stored in ram (for speed) or in a DB for clustering support. Unfortunately, CherryPy's sessions only support PostgreSQL, which means they're not a valid solution for TurboGears.

Furthermore, one of the design goals I was given was to avoid using sessions.

And since most web applications are not clusters why force this on them?

If you're really worried about scalability (like enterprise apps) you *will* be deploying in a clustered environment. That's what makes it an enterprise-class solution. Without clustering you're dead when one machine goes down or gets thrashed by a runaway thread.

--

Jeff Watkins

http://newburyportion.com/


In the USDA study [of the meat packing industry conducted in 1996] 78.6 percent of the ground beef contained microbes that are spread primarily by fecal material. The medical literature on the causes of food poisoning is full of euphemisms and dry scientific terms: coliform levels, aerobic plate counts, sorbitol, MacConkey agar, and so on. Behind them lies a simple explanation for why eating a hamburger can now make you seriously ill: There is shit in the meat.

-- Eric Schlosser, Fast Food Nation



Reply via email to