If your systems authentication consists of simply being logged in or out, then ACL would definitely be overkill. Auth can be set up for this in about 5 mins, and can be expanded upon if necessary. Don't forget to take into account the possibility of the requirements changing down the road though.
http://teknoid.wordpress.com/2008/10/06/introduction-to-cakephp-features-build-an-app-in-less-than-15-minutes/ http://teknoid.wordpress.com/2008/10/08/demystifying-auth-features-in-cakephp-12/ http://bakery.cakephp.org/articles/view/minimalistic-group-based-access-control-in-5-mins By default Cake starts a session for every visitor, and at a few points in its core uses the session. Disabling the session will most likely have a few unexpected side effects, like no flash messages or automatic Auth redirecting. On Oct 31, 3:37 am, centr0 <[email protected]> wrote: > My application only has 1 level of authentication. Would ACL be > overkill for this? Will the Auth component take care of this? > > Does CakePHP hold sessions for anonymous users? If so, is there a way > not to track sessions for anonymous users that havent logged in/ > registered? > > TIA --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
