I'm developing an intranet for a citrix customer (basically means that everyone works on a pc that is on the same 100mb switch as the web server) and would like to know which idea would have less of a performance hit. Do I a store all user privalege details in a cookie on their local machine and update the info every time they log on or do I just access it directly from the access database? I'll be using the cookie approach to store the username anyway (Novell is in the equation and I cannot get the username from asp so I'd assume it is a problem with their Novell implementation and so asp.net won't be able to get either... I could possibily use javascript but thats by the by) but am uncertain as wether to bother putting privelage info in there as well. These are accountants and so not techies so I am not overly worried about them hacking into the cookie to edit it.
Is there another way of doing the same thing (avoiding session variables which are despised world over
)
Is there another way of doing the same thing (avoiding session variables which are despised world over
)