In most scenarios, this view state processing model works fine.
在多数案例中，这种检视状态处理模型都可正常运作。
For client applications, this is the desired behavior in most scenarios.
对于用户端应用程序而言，这是多数情况下所需要的行为。
Namespaces should contain types that are used together in most scenarios.
命名空间应包含在大多数情况下要一起使用的类型。
Indeed, the Frightful Five are so well-protected against start-ups that in most scenarios, the rise of new companies only solidifies their lead.
的确，面对初创公司，“五恶人”被保护得非常好，以至在大部分情况下，新公司的崛起只会巩固它们的领导地位。
In most scenarios, however, you will eventually reach a point where your application should not continue until the database operation is complete.
但是，在大多数方案中，最终将到达一个临界点，此时，应用程序在数据库操作完成后才应继续。
This might not be an essential feature, but it's one of the most desirable features because this makes the same services consumable in different scenarios.
这可能不是最基本的功能，但却是我们最想要的功能之一，因为这样可以在不同的场景中使用相同的服务。
In most real life scenarios that I have encountered, a strongly typed service interface is a better fit.
在我所遇到的大多数实际场景中，强类型服务接口更为适用。
In practical terms this means that most of the scenarios that have been tested in the past will gradually be brought into the WSTF.
就实践而言，这意味着过去测试的大多数场景将逐步被带入WSTF。
In most Web application development scenarios, convenience often leads developers to implement security in their application logic.
在大多数Web应用程序开发场景中，开发人员通常都会出于便利性的考虑而在他们的应用程序逻辑中实现安全性。
The Spring Core's robust transaction infrastructure makes transaction management easier in most real-world development scenarios.
Spring核心包的健壮的事务基础设施使绝大部分真实开发场景中的事务管理更加轻松。
In the next part of this series, I will discuss the common scenarios, the relevant solution patterns for these scenarios, and will look at the most common issues affecting these scenarios.
在这个系列的下一个部分中，我将讨论一些通用的场景，以及与这些场景相关的解决方案模式，同时指出影响这些场景最一般的问题。
There may be scenarios where most of the data you require for reporting exists in one database with the exception of a few other key tables.
有可能存在这样的场景：您的报告需要的大部分数据都存在于一个数据库，但几个关键表除外。
In the most basic of interaction scenarios, the client and the server ORBs communicate directly with each other to satisfy application requests for remote resources.
在最基本的交互场景中，客户端和服务器OR B直接彼此通信，以满足应用程序对远程资源的请求。
Most business scenarios, regardless of their business goals, user roles, data, or industry focus, can be represented in the interaction model shown in figure 2.
无论业务目标、用户角色、数据或者行业焦点是什么，大多数业务场景都可以用图 2中的交互模型表示。
Since all of our built-in collection types implement this interface there are no perf gains in the most common scenarios.
自从我们所有的内建集合类型实现了此接口以后，在那些最常见场景下并未获得任何性能收益。
This policy may be most useful in migration scenarios when coupled with some sort of clean-up mechanism associated with the alternate source.
在迁移场景中，当与关联于备用源的某些类型的清理机制结合使用时，这个策略可能是最有价值的。
Most business scenarios, regardless of their business goals, user roles, data or industry focus, can be represented in the preceding interaction model.
无论业务目标、用户角色、数据或者行业焦点是什么，大多数业务场景都可以用上述交互模型表示。
Although the testing addresses many scenarios, it's important to note that the parameters in the environment are rigid and for the most part uniform.
尽管测试能解决许多场景中碰到的问题，但是要注意每个环境的参数都是不能改变的并且在大多数情况下是统一的。
However, while exchanging a hash table is easy and supported out of the box, it is only appropriate to use in the most simple of interoperability scenarios.
然而，尽管基于哈希表的数据交换很简单并且切实可行，但它只适合应用于最简单的互操作场景中。
While there are some scenarios in which failure is potentially devastating, or perhaps even life-threatening, most of the time it isn't.
有一些实例，失败是潜在性的灾难，或可能是威胁生命的，但大多数时候不是这样。
In Part 2 I will discuss different estimation scenarios, what methods are best under what circumstances, and how to most efficaciously apply them.
在第2部分，我将讨论不同的评估情况，即在什么环境下最好采用什么样的方法，以及如何最有效地使用这些方法。
Although ASP.NET applications never run in-process within the Web server, in the most common scenarios, the overall performance is close to that of in-process applications.
虽然ASP.NET应用程序从不在服务进程内工作，但在大多数情况下，总体性能与工作在服务进程内相差不大。
While your odds of having a heart attack are much higher than finding yourself in most of these scenarios, strange things happen every day.
尽管你心脏病突发的概率要远远大于你遇到上述“奇遇”的概率，然而，这些事情每天都在上演。
This is one of the most popular scenarios presented by mainstream PLM vendors in the context of design and engineering collaboration.
这是主流plm供应商在设计和工程协作功能中最常展示的内容。
For most of the use case scenarios in virtual Spaces, avatars that can be easily identified as real-life-us, are preferred.
对于虚拟空间中的多数用例来说，最容易识别真实身份的角色最受钟爱。
However, even the most mundane and vanilla scenarios get a boost when you toss in a vacuum named Henry that has a face on it.
然而，爆笑的事情发生在一台名叫“亨利”的人面吸尘器身上。
In most B2B scenarios the transactions are more frequent (it is common for a company to send several dozen orders to a supplier every day) so you want to automate the transactions as much as possible.
在大多数B2B的环境中，事务的发生频率更高(通常某家公司在一天之内给供应商发送的订单有几打)，因此您需要使事务尽可能的自动化。
I'll talk more about how adding metadata effects the modularity of AOP systems, as well as the scenarios where metadata is most beneficial in Part 2 of this article.
我将进一步讨论添加元数据如何影响AOP系统的模块化，并在本文的第二部分中讨论元数据发挥最大作用的场景。
One of the most commonly encountered scenarios in SOA projects involves exposing existing transactions as Web services.
SOA项目中最常遇到的一个情况就是将现有事务作为Web服务公开。
The ARM agent is most useful in these scenarios.
ARM代理在以下情景中最有用。
应用推荐