I am building a web application.  The authentication will be managed by the website, that is not my concern.  What i need to store is the UserID in some place. 
Once they open the application I will be able to get their UserID.  I was previously using a Session variable to store this.  Can I create a class say:
static string _UserID;
public static string UserDetails
{
    get
    {
        return _UserID;
    }
    set
    {
        _globalValue = \\value from webpage;
    }
}
and use UserDetails._UserID instead of assigning it to a session variable?!
The website's session server is not very reliable so I thought I could use this way.
Will this work?
I learnt from the answers that the variables will be overwritten for each user which is not what I want!!
Will it be the same scenario if i create an instance of this class in handler and assign the UserID to it??
are there any other way where I can make its scope limited only to one user i.e UserID with which I login should be same and if new user login to the application it must not be overwritten?? what is the disadvantage of using this method?? Is this method good if I use only one page and assign the object in the launch of the applciation ??