[Amit]

“Session memory but now I’m thinking I should only put in session those public attributes that need to retain the values and not the methods code.”

I’m a bit concerned with that statement… In terms of memory usage, your methods and code are not sitting in the session variable at all. Only a reference to the object. The methods are not copied along with each instance. the methods remain in the in-memory copy of the DLL (on copy for the whole application).

[Amit]

Unless this class holds a large amount of data it really should not matter so long as it is instantiated before you try to use it. Given this, creating the instance in the constructor would be the best way to ensure that the class is available when needed, otherwise if you use this class in several different methods you would need to check if the class has been instantiated and then create it if needed causing you to duplicate code

[Amit]

I started by HTML innfact i suck at it now, i used to be uber html coder, then i started PHP witch i still do, then i started modding a game called battlefield 1942, witch is my most favorite game of all time, then i wanted to learn c++ so i was given a book, at the beginning of this year, and im a quarter through it, its better than class cause u can do when u want Razz, but im not even a quarter and i wrote, in 3 minuts, an app that spells entered words backwards, and in 2 minuts a program that counts down from a number you enter, if you want code for eather of thses, im willing to give them, just PM me and i will freely send them to you