Hey all – I have an app where I’m authenticating the user. They pass username and password. I pass the username and password to a class that has a static method. For example it’m calling a method with the signature below:
public class Security { public static bool Security.Member_Authenticate (string username, string password) { //do stuff} } If I have 1000 people hitting this at once, will I have any problems with the returns of the method bleeding into others? I mean, since the methods are static, will there be issues with the a person getting authenticated when in fact they shouldn’t be but the person before them was successfully authenticated ASP.Net returns a mismatched result due to the method being static? I’ve read of issues with static properties vs viewstate but am a bit confused on static methods. If this is a bad way of doing this,what’s the prefered way?
This will not happen. When a method is Static (or Shared in VB.NET), then you’re safe as long as the method doesn’t rely on anything other than the inputs to figure something out. As long as you’re not modifying any public variables or objects from anywhere else, you’re fine.