Tom, When using session variables you are using cookies to identify this when opening a browser window, the problem is that cookies are small files that can NOT hold complex data so I find this strange coming from an IT guy.
I personally hate sticking things in the session variables, but if you could explain in a bit more detail the process. For example. 1) User logs in 2) User is checked for roles Etc.. I personally have a tag that hits the db every page hit, double checks the user is there and sets up the required roles etc. Now I noticed that you have Application.Users but you don't say how your getting this info in to this scope, I would maybe say that there is a problem there. If you would like to send me a copy of these codes so that I can see the application.users in action I might be able to help you out here. Regards Andrew Scott Technical Consultant NuSphere Pty Ltd Level 2/33 Bank Street South Melbourne, Victoria, 3205 Phone: 03 9686 0485 - Fax: 03 9699 7976 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom MacKean Sent: Friday, 8 April 2005 9:28 AM To: CFAussie Mailing List Subject: [cfaussie] RE: Weird session behaviour Our IT guy says that we are not using proxy caching, and does not think that this is the problem (I know nothing about proxy caching) Can you explain how it works? He says "why not use cookies?". I've never used cookies. Is it possible to store this kind of structure data in a cookie? How do you do it? Sorry for the newbie questions. Tom --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
