What is the advantage of saving a cookie and session information for a public CakePHP app (just the public-facing views, not admin views). Why should I save this information if there is no user data or preferences to keep track of?
I know for the admin views it's important to keep user info for log in and authentication purposes, and also to show Session messages (flash, errors). But for a read-only public view with no messages, no error validation, it's not needed right? Unless it's a recommended practice to always set cookies and save sessions, I'm looking for a way to set the cookie and session for admin routes only -- maybe as a beforeFilter type action? Right now I just disabled sessions and cookies in the core.php config file, but I'd prefer to enable just for the admin views. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
