Re: Random not so random

In article <D425483C2C5C9F49B5B7A41F89441547055523@postal.corporate.connx.com>,
"Dann Corbit" <DCorbit@connx.com> writes:

> A better way would be to seed a Mersenne Twister PRNG at server startup
> time and then use the same generator for all subsequent calls.
> http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html

> The period is exceptionally long, and it has many excellent properties.

I think you're slightly missing the point.  Every PRNG always returns
the same output swquence for the same seed, and that's the problem
with the current implementation: it might happen that two backends get
the same seed.