We separate the physical view and logic view of IR, and make algorithms work on the high-level logic view, and map the high-level algorithms into low-level IR through view transformations.
分离对象的物理视图与逻辑视图，隐藏物理视图的实现细节，使算法工作在高层的逻辑视图上，并通过视图变换将高层算法映射到低层中间表示上。
View rendering logic moves to the browser, which makes the server more stateless and thus more scalable.
视图显示逻辑向浏览器移动，这使服务器更为无状态且更加可伸缩。
View logic is concerned with presenting information to the user and collecting information from the user.
视图逻辑关注于向用户表达信息和从用户那里搜集信息。
The main differences come from how you place and implement business logic or view rendering logic.
主要的区别来自如何放置和实现业务逻辑或查看呈现逻辑。
This separation provides a number of benefits; to start, keeping your business logic completely separate from your control and view logic makes it very easy to add new views to your application.
这种分离提供了许多好处；开始时，保持您的业务逻辑同控制和视图逻辑完全分离，这使向您的应用程序中添加新的视图非常的容易。
Model refers to your data, View to your presentation layer, and Controller refers to the application or business logic.
模型指数据，视图指表示层，而控制器指应用程序逻辑或业务逻辑。
Such a design makes maintenance all but impossible, because whenever the view changes, you must change the model logic, and vice versa.
这样的设计使得维护几乎不可能实现，因为无论视图何时改变，您都必须改变模型逻辑，反之亦然。
The complete separation of view and controller logic plus the use of standard HTML templates makes the framework very easy to use, even for people not familiar with the MVC pattern.
把视图和控制器逻辑完整的分离有利于标准HTML模板的使用，这让框架非常容易的使用，甚至于对于那些不熟悉MVC模式的人来说也是如此。
The view then performs the logic required to determine the appropriate response before returning that response.
然后该视图在返回响应之前，执行确定适当的响应所需的逻辑。
The primary instance of the model is keeping long-term state and providing application logic; the copy used by the view is essentially a disposable data-access object.
模型的主实例保持长期状态，并提供应用程序逻辑；而视图使用的副本实际上是一个可任意使用的数据访问对象。
Often the view, especially when you're handling form data, demands some logic to display the right thing based on user actions and certain conditions.
视图经常(特别是当您处理表单数据时)要求一些逻辑来根据用户操作和某些条件显示正确的内容。
The big difference is that the view and control logic is separated into completely distinct layers.
最大的不同是视图和控制逻辑被分离成两个完全不同的层。
Figure 2 shows a simplistic view of the relationship between inputs, application logic, and notification methods or outputs.
图2显示了输入、应用程序逻辑、通知方法或输出之间的简单视图。
Placing the logic inside an action method does not guarantee that it will be executed prior to rendering because a page view is not always preceded by a user-triggered event.
将逻辑放在一个动作方法中并不能保证该逻辑在视图呈现之前得到执行，因为页面视图并不总是在用户触发的事件之后。
Since there is no business logic needed prior to rendering this view, we will simply invoke the Add Contact JSP directly, configuring it as a global forward instead of as an action.
因为在处理这个视图之前无需任何业务逻辑，所以我们只需直接调用添加联系人JSP（把它配置成全局转发而不是操作）。
J2EE provides constructs that allow view and control logic to be easily separated.
J2EE提供了一些概念使视图和控制逻辑能很容易的分开。
However, the IBM Business Integration Reference Architecture places such logic in the Process Services component, a view supported by the advice given in the Redbook.
然而，IBM业务集成参考架构将这种逻辑放置在流程服务组件中，该红皮书中提供了这种建议。
And putting entities' behavior in services or the view layer scatters the entities' core logic throughout the application, causing maintenance problems.
另外，把实体的行为放在服务或视图层中，会导致实体的核心逻辑分散在应用程序中的许多地方，导致维护问题。
MVC aims to separate view logic and UI components from application logic.
MVC 的目的在于将视图逻辑和UI组件与应用程序逻辑相分离。
Yet MVC requires that view components, such as JSPs, be free of logic.
然而MVC要求视图组件，比如JSP与逻辑无关。
Again, you can only view this flow logic correctly when working in the advanced editing mode in Business Modeler.
您同样只能在Business Modeler的高级编辑模式下正确地查看这个流逻辑。
View beans also let us separate presentation logic from our business logic, keeping HTML code out of our servlets and other control and model objects.
视图bean还允许我们把表示逻辑与我们的商业逻辑分离开来，将HTML代码放在servlet以及其它控件和模型对象之外。
From the user's point of view, Eclipse support has two problems: XM has its own logic for rebuilding projects and its own logic for reporting errors.
从用户的观点看，Eclipse支持有两个问题：XM有自己的项目重建逻辑和错误报告逻辑。
Typical Web services employ a remote presentation paradigm, meaning all view logic executes on the client, whereas the application logic and the data layer (controller and model) reside on the server.
典型的Web服务使用远程表示范例，这意味着所有的视图逻辑在客户机上执行，而应用程序逻辑和数据层(控制器和模型)则驻留于服务器上。
Last but not least, separating the description of the view and its associated behavior logic has never been easier, thanks to the build method on SwingBuilder.
最后但是也最重要的是，由于SwingBuilder的build方法，分离视图的描述与它相关联的行为逻辑变成再简单不过的事情了。
But in our case, because the servlet actually creates the downstream view, we need additional components to wrap our controller and model logic.
但在我们的示例中，因为servlet实际上创建了下行视图，所以我们需要另外的组件来包装控制器和模型逻辑。
In the article Bejeck is trying to create components with a mixture of inheritance and composition, and enforce separation of concerns, especially between view and business logic.
Bejeck在文章中试图创建混合了继承和组合关系的组件，实施分离关注点，尤其是分离视图和商业逻辑。
Alternatively, you could implement the view in the doView() method using prinltn logic
或者，也可以使用prinltn逻辑在doView()方法中实现视图。
Alternatively, you could implement the view in the doView() method using prinltn logic
或者，也可以使用prinltn逻辑在doView()方法中实现视图。
应用推荐