Requests that are known to be strictly read-only should use slave DBs for all queries

This would not apply to any request handler that *might* need to write; if there's any potential to write, we should stay on the master the whole time.

There might be some consistency issues with this (as users update information (hits master) then follow with a request to display that information (hits slave)), although our slaves are generally really close to the master.