|
|||
|
Hello,
if I want to want to provide lists and profiles of artists, locations and agencies, an url could look like: /artist/arstists_name (should deliver profile of artist named "artists_name") or /location (should deliver list of locations) I could route "/:type/:name" and use a CentralController which detects by Param("type") which profile-type to deliver instead of creation three differen Controller named ArtistController, LocationController, AgencyController etc.pp.; It would lead to conducting all request to one actionController, which seems to be a duplication of the FrontController-Pattern. Does this make sense? Dank und Gruß, frankx |
|
|||
|
This is a nice conception "problem". For your question, there is no good or bad solution at first.
To me, the decision would be based on the number of categories I have and the complexity involved when dealing with a category. If you have a hundred categories, I would certainly not create a hundred controllers! Good luck... even if luck won't help!! |
|
|||
|
Doesn't make sense to me...
if you have three urls /artist/artist_name, /location/location_name and /agency/agency_name why would you want them all in one controller? What would you achieve by that? It's not less coding than doing three controllers anyway. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|