Quote:
Originally posted by Redth
as for authentication... on the login form, authenticate the info against the database... then have a session variable like:
Session("IsLoggedIn") = "1"
Now, on every page which you want to authenticate the user, put something like this in the page load:
If Session("IsLoggedIn") <> "1" Then
Response.Redirect("Login.aspx")
End If
That was exactly how I plan to handle it now that I know that session variables won't kill performance. Thanks for backing up that decision.
Quote:
1. Use seperate objects and connections for each page... although one global connection in theory sounds good, you will run into problems with it. Besides, if you have a connection on each page, Connection Pooling will happen anyways, that is what it is designed for
Are telling me that .Net will pool the connections to the db by itself without me having to do anything?