10-03-2008, 04:22 PM
[eluser]jleequeen[/eluser]
@Rick
That makes the most sense to me, but it seems more and more I'm seeing examples where someone creates there URL structure on objects they've derived from their DB. To me, views can pull data from one or many models and break down really easily when you by default create a controller because you've added a new table to the database and want to put all that functionality into that table.
I'm just curious since you do use 1 controller per view almost all the time, do you end up with urls like the following?
http://www.yoursite.com/user_login
http://www.yoursite.com/user_profile
http://www.yoursite.com/user_list
or do you do subfolders where you can have user/login etc.?
Just curious?
@Rick
That makes the most sense to me, but it seems more and more I'm seeing examples where someone creates there URL structure on objects they've derived from their DB. To me, views can pull data from one or many models and break down really easily when you by default create a controller because you've added a new table to the database and want to put all that functionality into that table.
I'm just curious since you do use 1 controller per view almost all the time, do you end up with urls like the following?
http://www.yoursite.com/user_login
http://www.yoursite.com/user_profile
http://www.yoursite.com/user_list
or do you do subfolders where you can have user/login etc.?
Just curious?