Re: Persistent Sessions in DB connection for QZDASOINIT, implemented by Nathan

I have in the last few months been the user of a high -profile,
high-traffic web site
...
Essentially I'd like to avoid a similar situation where I'm
responsible
...
If there are no immediate brickwalls ahead in the planned scenario, then
keep it simple. I.e. a connection per user.

I'm not trying to put words in other people's mouths, but I'm not sure your conclusions are supported by the conversation. I think the big question is, what's "high-traffic". I think there is agreement that in low-traffic sites the one-connection-per-user approach works. I know I agree with that, and I'm a proponent of not doing sites that way :-). I think there is also agreement that the one-connection-per-user approach would _not_ work for mega-traffic sites like Amazon, Facebook or MySpace. So the question is, what's "high-traffic"? Is it 100 simultaneous users? Nope. 1000? Maybe... 10,000 Probably...

-Walden