The first one is client layer.
第一层是客户层。
The client layer controls the transaction scope.
客户端层控制事务作用域。
Client Layer - used by application to communicate with SQL azure.
客户端层——应用程序会使用它来与SQL Azure通信。
Typically you need to use programmatic transactions in the client layer.
通常，您需要使用客户端层中的程序化事务。
The latter contains three parts: data layer, service layer and client layer.
数据处理部分主要分为数据层、服务层和客户层。
The prototype has three layers: the client layer, the agent layer and the server layer.
本系统采取三层体系结构，分别是客户端，中间代理层和分布的服务器层。
Notice in this strategy that both the client layer and the API layer contain transaction logic.
注意，在此策略中，客户端层和api层包含事务逻辑。
If the application's API layer is too fine-grained, you have to invoke both methods from the client layer.
如果应用程序的api层非常细粒度化，那么您需要调用客户机层中的两个方法。
Such variations might be caused by a gap in the systems model or by a unilateral change in the client layer.
此类变体可能源于系统模型的差异或者客户层的擅自变更。
In this scenario, the transactional unit of work must reside in the client layer to ensure an atomic unit of work.
在此场景中，事务工作单元必须位于客户机层中以确保自动化的工作单元。
Only methods in the client layer and the API layer of the application architecture should contain transaction logic.
只有应用程序体系结构的客户端层和api层中的方法才应该包含事务逻辑。
Like the API layer strategy, the High Concurrency strategy frees the client layer from any transaction responsibility.
与api层策略类似，High Concurrency策略释放了客户机层的任何事务责任。
The transaction context from the client layer will propagate to the API layer methods and all methods invoked under the API layer.
客户端层中的事务上下文将传播给API 层方法以及在 API 层中调用的所有方法。
But this flexibility comes with a price - namely, that the client layer is restricted to a single request for a given transactional unit of work.
但是这种灵活性需要付出一定代价—即客户机层仅限于对给定事务工作单元的单一请求。
With the API layer transaction strategy, it's not the end of the world if you start a transaction at the client layer during a refactoring effort.
对于api层事务策略，您在重构过程中在客户端层上开始一个事务并不会引起灾难性后果。
The Client Orchestration transaction strategy is used when multiple server-based or model-based calls from the client layer fulfill a single unit of work.
当来自客户机层的基于多服务器或基于模型的调用完成单一工作单元时，将使用ClientOrchestration事务策略。
When you use programmatic transactions in the client layer outside of the context of a stateless session bean, you don't need to set the transaction type.
在无状态会话bean上下文外部的客户机层中使用编程事务时，您不需要设置事务类型。
The API-layer methods contain transaction directives instructing the transaction manager to incorporate and use the transaction scope started by the client layer.
API 层方法包含一些事务指令，它们指示事务管理程序整合和使用由客户端层开始的事务作用域。
The exception to this rule is if the client business delegate in the client layer controlling the transaction scope is managed as a Spring bean by the Spring Framework.
此规则的例外情况是，管理事务作用域的客户端层中的客户端业务代理由SpringFramework托管为Springbean。
The client Orchestration transaction strategy is useful when most of the requests from the client layer require multiple calls to the API layer to complete a single LUW.
当来自客户端层的大多数请求都需要向api层发起多个调用才能完成一个LUW时，客户端编排事务策略将非常有用。
The business data information is maintained and manipulated intact in both the application and database layers, and as you will see in Part 3, even in the client layer.
在应用程序层和数据库层中都按原样维护和操作业务数据信息，而且您将第3部分中看到，甚至在客户机层中也是如此。
As the name suggests, this strategy is used when the application's client layer must make one or more calls to the API layer to complete a single transactional unit of work.
我的建议仍然是，在应用程序的客户端层必须向api层发起一个或多个调用才能完成单个事务工作单元时使用此策略。
This means that the protocol used to communicate between the client layer and the API layer, as well as the type of client, play an important role in the application architecture.
这意味着用于在客户端层和api层之间进行通信的协议以及客户端的类型在应用程序体系结构中发挥着重要的作用。
As I said earlier, one of the biggest restrictions with this transaction strategy is that the client layer must be able to start a transaction and propagate it to the API layer.
如前所述，这种事务策略的最大一个限制就是，客户端层必须能够开始一个事务并将它传播给api层。
As you can see from Listing 4, if an exception is thrown in either of the update methods, it is the client layer method's responsibility to do the necessary transaction rollback.
从清单4中可以看到，如果任何一个更新方法抛出异常，则客户端层方法将负责执行必要的事务回滚。
The bottom hardware driver is written by Lingyang chip microcomputer AL and the USB protocol & client layer application program written by Lingyang chip microcomputer C language.
它的底层硬件驱动程序用凌阳单片机汇编语言编写，USB协议和应用层程序用凌阳单片机C语言编写。
Storing session state in the client using HTTP cookies or hidden form fields has significant security risks — it exposes a part of your application internals to the untrusted client layer.
在客户端用HTTPcookie或者隐藏表单字段存储会话状态有很大的安全风险——它将应用程序的一部分内部内容暴露给了非受信任的客户层。
If the client layer is making remote calls to the API layer, the client layer must use a protocol and transaction manager that supports the propagation of a transaction context (such as RMI-IIOP).
如果客户端层向api层发起远程调用，则客户端层必须使用支持传播事务上下文的协议和事务管理程序(比如说rmi - IIOP)。
The client layer in this regard can refer to calls made from a Web framework, portal application, desktop system, or in some cases, a workflow product or business process management (BPM) component.
此处的客户机层可以表示来自Web框架、门户应用程序、桌面系统或工作流产品或业务流程管理(BPM)组件的调用。
For this reason, they must use a transaction attribute of MANDATORY, indicating that a transaction is needed by the method but it should have been started elsewhere (such as in the client layer).
基于此原因，它们必须使用MANDATORY事务属性，这表示方法需要事务，但不应该在别处开始它(比如说在客户端层中)。
应用推荐