-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
> Or longer? In a web application it's possible that the "next" request > happens before the slave is synced. > > In a web application with many application servers (and non-sticky > sessions) the next request could be handled by any process on any > web server. It would seem that something would need to be in the > session or request (url) to indicate that a write just happened > so that all reads (from that web-session) need to go to the master > for some amount of time to allow the slave to sync. Doesn't > sound too pretty. Right. We've tackled that situation before, and made a working prototype to do such a thing (using session variables), but the complexity becomes quickly not worth the cost of just defaulting to the readwrite handle on all but the safest and simple queries. Which ends up being a lot of them. - -- Greg Sabino Mullane [email protected] End Point Corporation PGP Key: 0x14964AC8 200907121727 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkpaVTMACgkQvJuQZxSWSsh/pwCg6o5LyQDZAp8EZxGcx+O9rzWh /hUAoOHGFfF9vy3vPpFDr5X6sfDnSDBQ =1HUH -----END PGP SIGNATURE-----
