I mention these rules again because they also apply to the Client Orchestration transaction strategy.
我再次提到了这些规则，因为它们同样适用于客户端编排事务策略。
Anybody with an HTTP client and enough knowledge of our sync strategy should be able to synchronize with a data service.
使用HTTP客户端，以及具备我们的同步策略充足知识的任何人都可以使用数据服务实现同步。
The architecture in Figure 1 implements the Client Orchestration transaction strategy.
图1中的体系结构实现了客户端编排事务策略。
Adjust our keyword strategy based on client feedback.
根据客户反馈调整我们的关键词策略。
Unfortunately, the malicious test client cannot be optimized by this strategy.
遗憾的是，此策略不能对恶意的测试客户机进行优化。
I've given this strategy its name because in most cases, back-end processing functionality is exposed to client applications through the use of interfaces or an API.
我将这个策略指定为这个名称的原因是，在大多数情况下，后端处理功能会通过使用接口或API向客户应用程序公开。
And observe that the transaction strategy is spread throughout the layers below the client, but not completely.
并且事务策略遍布于客户机下面的层中，但这不是绝对的。
Furthermore, using REQUIRED in the API layer methods means that a transaction could be started by the API layer, thereby violating the main principles of the Client Orchestration transaction strategy.
此外，在api层方法中使用REQUIRED意味着事务可以由api层开始，因此这违反了客户端编排事务策略的主要原则。
Even so, the first rule in strategy is to pay critical attention to the needs and desires of the client and your organization's ability to fulfill those needs.
即使这样，战略中的首要规则是重视客户的需求和愿望，以及您组织的能力，从而满足那些需求。
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层发起一个或多个调用才能完成单个事务工作单元时使用此策略。
In the meantime, a client can be configured to connect to many servers, organized in a hierarchy of server connection pools that defines an effective failover strategy.
同时，一个客户端可以配置多个可连接的服务器，通过将这些服务器组织成一个层次结构来定义一个有效的故障转移策略。
Don't be tempted to mix the Client Orchestration strategy and API Layer strategy in the same application to try to solve every permutation in your application architecture.
不要尝试在相同应用程序中混合客户端编排策略和api层策略，以期解决应用程序体系结构中的所有变化。
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时，客户端编排事务策略将非常有用。
I typically ask the architect or technical lead in a client engagement to describe their project's transaction strategy.
我经常会让与客户接触的架构师和技术总监描述他们项目的事务策略。
Notice in this strategy that both the client layer and the API layer contain transaction logic.
注意，在此策略中，客户端层和api层包含事务逻辑。
If you do have clients that do not support transactions but you find the client Orchestration transaction strategy seems like a good fit, you may have to do some refactoring.
如果您的客户端不支持事务，但您发现客户端编排事务策略非常合适，那么需要执行一些重构。
The following rules and characteristics apply to the Client Orchestration transaction strategy.
以下规则和特性适用于客户端编排事务策略。
This strategy is difficult to implement, takes longer to develop and test, and is more error prone than the API Layer or Client Orchestration strategies.
此策略难以实现，并且需要更长的时间进行开发和测试，并且比api层或ClientOr chestration策略更易于出错。
In this article, I'll describe the Client Orchestration transaction strategy, which I introduced briefly in "Models and strategies overview."
在本文中，我将讨论客户端编排事务策略，而我之前在“模型和策略概述”一文中简要介绍了这方面的内容。
This transaction attribute is used in the Client Orchestration transaction strategy described in this article's next section.
这个事务属性应用于本文下一部分将要讨论的Client Orchestration事务策略。
For a web service client, this strategy usually works across multiple web containers since the client code does not depend on any web service deployment descriptors.
对于Web服务客户机，这个策略通常能跨多个web容器工作，因为客户机代码并不依赖于任何Web服务部署描述符。
With this strategy, the GWT client sends the RESTful Web service request to the RPC remote service, which then passes the request to the RESTful Web service server.
按照这种策略，GWT客户机把RESTfulWeb服务发送给RPC远程服务，RPC远程服务把请求传递给RESTful Web服务服务器。
Like the API layer strategy, the High Concurrency strategy frees the client layer from any transaction responsibility.
与api层策略类似，High Concurrency策略释放了客户机层的任何事务责任。
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事务策略。
General strategy: Client-server strategy.
一般策略：客户机——服务器策略。
So, in other words, to use my strategy, simply write one test case class, and then always deploy to both the client and the server.
所以，换句话说，要使用我的策略，只需编写一个测试案例类，然后总是将其部署到客户机和服务器就可以了。
I could point out other issues, for instance, where are the client side validations, adaptable workflow, and dynamic strategy pattern for the controller?
我还能指出其他问题，例如，控制器的客户端验证、可适用工作流程和动态策略模式在什么地方？
Back to the original point: with the API layer transaction strategy, the client must not make multiple calls to the API layer in a single unit of work requiring a transaction.
回到原点：对于api层事务策略，客户机绝对不能在涉及事务的单一工作单元中对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层。
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层事务策略，您在重构过程中在客户端层上开始一个事务并不会引起灾难性后果。
应用推荐