关注的分离。
MVC is all about proper separation of concerns.
MVC最重要的就是合理的分离关注点。
Separation of Concerns and Configuration files.
关注点分离和配置文件。
There was no layering and no separation of concerns.
各种关系之间没有任何分层和分离。
This is called, in a loose sense, a separation of concerns.
这在松散意义上称为关注点分离。
Remember that separation of concerns thing mentioned earlier?
还记得早先提到的关注分离吗？
This is another example of the separation of concerns in JSF.
这是在JSF中分离关注点的另一个例子。
A key characteristic of an ESB is separation of concerns.
ESB的关键特性是分离关注点。
Separation of Concerns in the Deployment Process: What vs. how.
区分部署过程中的担忧：为什么vs。
Keep separation of concerns by separating the interfaces from each other.
通过相互分离接口保持关注点的分离。
Finally, delegating logic often leads to a cleaner separation of concerns.
最后，委派逻辑通常会得到更干净的关注点分离。
It also allows for an improved separation of concerns in the finished system.
它还允许在最终完成的系统中实现更好的关注分离。
Separation of concerns refers to extracting the code into various layers
关注点分离指把代码提取到不同的层
Separation of concerns simplifies integration architecture implementation.
关注点分离简化了集成体系结构的实现。
This tutorial will demonstrate two implementations of this separation of concerns.
这篇教程将展示关注点分离的两个实现。
There is a completely new separation of concerns among the three market layers
有一种全新的分级方式将对于市场中分为三个不同级别
The third principle of a modularity framework is the principle of separation of concerns.
模块化框架的第三个基本原理关注分离。
The latter method would increase maintainability even more through separation of concerns.
后面的方法将进一步通过分离关系来提高可维护性。
This yields a true separation of concerns, enabling the repurposing of software components.
这就产生了关系的分离，使软件组件可以被重用。
By nature, the MVC pattern is highly testable and encourages good separation of concerns.
MVC模式天生就是可测试的，而且鼓励对关注点的分离。
Achieve a clear separation of concerns between architectural building block responsibilities.
在架构构建块职责之间可以实现一个清晰的关注点分离。
Respecting separation of concerns, even if initial size of the two concerns is rather unequal.
注重关注点分离，即使两个关注点的初始大小差别很大。
But that is the whole point of separation of concerns that we have discussed throughout these columns.
但它是分离关注点的关键，我们在这些专栏中讨论过这个问题。
It is designed to create a separation of concerns between application protocols and security protocols.
它用于创建应用程序协议和安全协议之间的分离关系。
Through separation of concerns, integration requirements are decomposed into more granular services.
通过关注点分离，可以将集成需求分解为更细粒度的服务。
You can leverage this separation of concerns to test their behavior separately from the crosscutting specification.
可以利用这种关注点的分离分别测试横切规范及它们的行为。
And with this natural separation of concerns, the back-end work will either be outsourced, or it will be automated.
并且通过这种关系的自然分离，后面的工作将要么是外包的，要么可以自动化。
This implies that you need to maintain separation of concerns and to group like calls within a deployment unit.
这意味着需要保持关注点分离，并且需要在部署单元内像调用一样分组。
This separation of concerns means you can change one component with zero to minimal impact on other components.
采用关注点分隔原则意味着，对一个组件的修改对其他组件的影响非常小，甚至没有影响。
This functionality enables you to implement one of the key characteristics of an SOA-based ESB: separation of concerns.
这一功能性使您能够实现基于soa的esb的主要特性之一：分离业务。
应用推荐