I agree with Chris, it really doesn't matter which you do first, using functions like beforeRender and beforeFilter you can easily add your authentication in one place after your site is complete. But then again there's not reason not to do it first either. Just whatever you're preference is I guess.
On Jan 9, 2:34 pm, Robby Anderson <[EMAIL PROTECTED]> wrote: > I used some of Chris's links, so I can recommend them. :) > > Personally, I'm building out user security, authentication, access > control, session management, logging and testing first. They're all > pretty important elements, and I want to make sure they're right (or > at least working) before I move on to other things. (We're going to be > processing a lot of confidential data, and handling that properly is > at least as important as other functionality.) Luckily, Cake has most > of that kind of stuff built in or easily added, so its not like > building that out is going to take weeks. > > Also, if its your first tour in Cake (like it is mine), learning those > elements first will give you a really good idea of how the framework > is designed and operates, and will probably make the rest of your app > that much better in design. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
