Is it thread safe to set Active Resource HTTP authentication on a per-user basis?
Active Resource can make use of HTTP authentication set at the class level. For instance: class Resource < ActiveResource::Base end Resource.user = 'user' Resource.password = 'password' or Resource.site = "http://user:password@site.com/" But what if I use different HTTP authentication based on which user is logged in? If I change Resource.user and Resource.password, is that going to cause a race condition where requests from one thread suddenly start using the authentication of a user whose requests are running simultaneously in a different thread? Or is this a non-issue (as long as I reset