Timeline for answer to Avoiding coupling by Steven Jeuris
Current License: CC BY-SA 3.0
Post Revisions
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 26, 2011 at 15:45 | comment | added | Steven Jeuris | Great questions in your update! Let me know if my update somewhat answered them. ;p | |
| Nov 26, 2011 at 15:44 | history | edited | Steven Jeuris | CC BY-SA 3.0 |
added 1214 characters in body
|
| Nov 26, 2011 at 15:26 | comment | added | Seralize | Have a look at question #2 and I won't need to repeat myself here :) | |
| Nov 26, 2011 at 15:22 | comment | added | Steven Jeuris |
Yes, but not the business logic dots. ;p This is the line of code in the controller which worried me: if (! $word_id = $wordpicker->getRandomWord()) And the subsequent action you do then: // No more words left - game over! ... $game->deleteSession($game_info['id']);. That is definitely business logic and should be in your model!
|
|
| Nov 26, 2011 at 15:17 | comment | added | Seralize | This is exactly what I'm trying to achieve, but no matter how I twist and refactor it I only see the Controller as the solution, because it's the only place where I can "glue the application" together without coupling up the model. This is why I decided to ask for help. Call it the "index/client" if you will, but I have gotten the impression that I should not make a 'Model which connects the dots', that's what the Controller is for in the first place. | |
| Nov 26, 2011 at 15:15 | history | answered | Steven Jeuris | CC BY-SA 3.0 |