Re: Understanding MVC Architecture

Great ideas. I will see about pushing more into the models.  I have not
really done much with the router, but that gives me some ideas on how I
can do some things.

The data is fairly normalized, I am sure there is room for improvement.
But it needs to scale.
Basic premise is Users manage their profile, and can do a few things.  
Users can create organizations. The User/Owner of the Organization can
manage it.  Users can join Organizations.   Users can join multiple
organizations and have different roles.
If you are familiar with facebook groups then this concept is part of my
site.  I an not trying to recreate facebook or anything like that, but
some of the features of signup, moderation or manage the group, are a
good analogy. The main point is that it has to scale and that there are
several many to many tables.

Which brings up another question - I had some challenges getting the
multiple roles and ACL working. So, I have basically used Controller
based authorization and isAuthorized routines. This works well.  The
documentation talks about you could go to a model based authorization.  
I assume it works the same, except that the isAuthorized routines will
be in the Models instead of the controllers.  I can't seem to find a lot
of examples of why to do this?  I don't know if this would be a good
idea or not.  Do you have any ideas or thoughts about this?

Thanks again for the help.

---

View this message in context: Re: Understanding MVC Architecture
Sent from the CakePHP mailing list archive at Nabble.com.

--
Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions.
 
 
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php