Both, controller and view, should never use domain objects, e.g. entities (as part of the domain model) directly. They communicate (separately) with the domain model only through application services (also named use cases). These services may delegate (multiple) tasks to (multiple) domain services. Which, in turn make use of the domain objects (entities). If external components and/or services are needed (like the ones in the persistence layer, e.g. repositories, datamappers, for example), then the connection between the domain model and them is made through the use of corresponding interfaces. These also are part of the domain layer.

視圖不應(yīng)該訪問控制器.為什么要這樣做?控制器解釋用戶發(fā)送的請求(通過 HTTP 協(xié)議，在 Web 應(yīng)用程序中)并將所有域相關(guān)的工作推遲到域中的服務(wù)層，將請求數(shù)據(jù)傳遞給它.所以控制器只影響域?qū)拥淖兓?/strong>.另一方面，視圖僅從域?qū)诱埱髷?shù)據(jù).它也通過服務(wù)來做到這一點(diǎn).所以視圖從域中讀取.因此，在您的代碼中，視圖應(yīng)該只接收 $m 作為參數(shù).

第二種是，在視頻中，表示層要處理和顯示的數(shù)據(jù)從控制器通過域?qū)?strong>推送到表示層.現(xiàn)在試著想象一下，演示者依賴于交互者(實(shí)際上是一個(gè)應(yīng)用服務(wù)，一個(gè)用例).例如.從呈現(xiàn)者指向領(lǐng)域?qū)拥募^描述了一種依賴關(guān)系，而不是一種繼承關(guān)系.然后演示者的作用是將信息拉出域?qū)?與上面介紹的 Web MVC 的類比是顯而易見的.

The second one is, that, in the video, the data to be processed and displayed by the presentation layer is pushed from the controller through the domain layer to the presentation layer. Now try to imagine yourself, that that presenter depends on an interactor (which, actually is an application service, a use case). E.g. that the arrow pointing from the presenter to the domain layer describes a dependency relation, instead of an inheritance one. Then the role of the presenter will be to pull information out of the domain layer. The analogy with the web MVC presented above is then obvious.

資源:

主題演講:失落歲月的建筑 - 給出的演示文稿由 Robert Martin 提供，根據(jù) Creative Commons Attribution ShareAlike 3.0.

Keynote: Architecture the Lost Years - Presentation given by Robert Martin, licensed under a Creative Commons Attribution ShareAlike 3.0.

示例 1(在 index.php 中):顯示數(shù)據(jù)

用戶在瀏覽器的地址欄中引入 URL http://localhost/questions/12345 并期望一個(gè)帶有問題和多個(gè)評論的 html 頁面.因此 HTTP 方法是GET".所以不需要控制器，只需要一個(gè)視圖(用于從域模型中讀取和顯示數(shù)據(jù)).

The user introduces the URL http://localhost/questions/12345 in the address bar of the browser and expects a html page with a question and multiple comments for it. Therefore the HTTP method is "GET". So no controller is needed, but only a view (for reading and displaying data from the domain model).

<?php

namespace TestMvcExample;

use LibHttpMessageResponse;
use LibRouterRouteCollection;
use LibHttpMessageServerRequest;
use LibHttpMessageEmitterResponseEmitter;

/*
 * -----------------------------------------
 * Before dispatching by a front-controller.
 * -----------------------------------------
 */
$routes = new RouteCollection();
$routes->add('GET', '/questions/{id:d+}', [
    'view' => [QuestionsView::class, 'index'],
]);

$request = new ServerRequest('GET', '/questions/12345' /* , other args */);
$response = new Response(/* args */);

/*
 * ------------------------------------------------------------------
 * Dispatched by a front-controller.
 * Route params are saved into the attributes list of server request.
 * ------------------------------------------------------------------
 */
$view = new QuestionsView(new Template(), new QuestionsService(), new CommentsService());

$response = $view->index($response, $request->getAttribute('id'));

/*
 * ----------------------------------------
 * After dispatching by a front-controller.
 * ----------------------------------------
 */
$responseEmitter = new ResponseEmitter();
$responseEmitter->emitResponse($response);

示例 2(在 index.php 中):更新和顯示數(shù)據(jù)

在 URL http://localhost/questions/edit/12345 上，用戶編輯帶有屬性 action="/questions/update" 的表單中的問題并點(diǎn)擊提交按鈕更新".因此 HTTP 方法是POST".因此需要一個(gè)控制器(用于更新模型層)和一個(gè)視圖(用于從模型層讀取和顯示數(shù)據(jù)).

At URL http://localhost/questions/edit/12345 the user edits the question in a form with attribute action="/questions/update" and clicks the submit button "Update". Therefore the HTTP method is "POST". So both a controller (for updating the model layer) and a view (for reading and displaying data from the model layer) are needed.

您可以更改為其他要求，而不是僅使用視圖.例如，要使用演示者和視圖，兩者共享一個(gè)視圖模型.

Instead of only using a view, one can change to other requirements. For example, to use a presenter and a view, both sharing a view-model.

<?php

namespace TestMvcExample;

use LibHttpMessageResponse;
use LibRouterRouteCollection;
use LibHttpMessageServerRequest;
use LibHttpMessageEmitterResponseEmitter;

/*
 * -----------------------------------------
 * Before dispatching by a front-controller.
 * -----------------------------------------
 */
$routes = new RouteCollection();
$routes->add('POST', '/questions/update', [
    'controller' => [QuestionsController::class, 'updateQuestion'],
    'view' => [QuestionsView::class, 'getQuestionUpdated'],
]);

$request = new ServerRequest('POST', '/questions/update' /* , other args */);
$response = new Response(/* args */);

/*
 * ----------------------------------
 * Dispatched by a front-controller.
 * ----------------------------------
 */
$questionsService = new QuestionsService();

$controller = new QuestionsController($questionsService);
$controller->updateQuestion($request);

$view = new QuestionsView(new Template(), $questionsService);

$response = $view->getQuestionUpdated($response, $request);

/*
 * ----------------------------------------
 * After dispatching by a front-controller.
 * ----------------------------------------
 */
$responseEmitter = new ResponseEmitter();
$responseEmitter->emitResponse($response);

這篇關(guān)于MVC:這是初始化的正確順序嗎?調(diào)用 MVC 層的文章就介紹到這了，希望我們推薦的答案對大家有所幫助，也希望大家多多支持html5模板網(wǎng)！