Pavan, Are you storing non-redundant data in session? I mean, you could intelligently store all common variables (which are common to all users) in static objects, and user specific data (username, company name) in session. Say for example, user has color choices to make. But, he sticks to default color provided. Then, you could store this default color value in session. On contrary, if you have user chose color, then you could store them in session level objects, (all colors go as one static object each) and associate user choice to the static object. Here, you would not be duplicating data. As a second choice, You could store key-value pairs of user choice in static objects, and re-use them as needed. (like username;company;colorchoice#username2;company;colorchoice). what i suggest is to stick a design as first one, and consider moving redundant information, and non-redundant information and then going with using. HTH, venkat.Murthy |
