>To make what you're trying to do easier, I recommend that you store all your >session data within a structure, then copy that structure around as needed. >There are two reasons for this. First, if you don't do that, you'll have to >loop over your session variables to write them to the Session scope. Second, >the Session scope contains some data you wouldn't want to overwrite, like >the token values used to match a session with a browser.
So, are you saying that I should copy over to session.user (will this go in the session scope even then or will it still be in the variables scope?) and just leave it there? Currently all my apps check for session.dn and I'd have to change them to session.user.dn in this case, right? thanks for answering - I was getting worried. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:221517 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
