This content has been marked as final. Show 3 replies
Session variables are useful irrespective of login requirements. I can't remember ever doing it myself, but I see no reason to not make an object a session variable if it suits the needs of your app.
For your specific post, I'm not sure why you would use session variables for products to determine a timeout, but it's not my application.
I guess I should have been more specific, our products/services contain multiple pages of forms to gather the proper information, that is why we use a session timeout to protect the users information without actually being logged into the system. I have started building it with the session object and it is working well, im looking forward to seeing how it turns out. Thanks for the input it is certainly appreciated.
We've been storing CFCs in the session scope for years, and it works great for the most part.
There is one caveat (which is no longer an issue if you're using ColdFusion 8). And that is...if you're using ColdFusion 7 or earlier in a clustered environment...session replication from one cluster node to another will corrupt your session-based CFCs, since previous to CF 8, CFCs were not serializable.
So...if you're on ColdFusion 8, great! No worries. If not, and you're using ColdFusion 7 or earlier, but you're NOT in a clustered environment, than no worries there either. You only need to worry if you're using CF 7 (or earlier) in a clustered environment.
I hope this helps.