梦剧场。场景二序曲19。
场景二：怎么把阴暗的仓库改装成时尚又明亮的工作室，且还要保留它的历史感？
Scene 2: How to make the dark and rusty warehouse become fashionable and bright with the retention of its history?
场景二：哈利走进卧室时，一个叫多比的家养小精灵正等着他。多比警告哈利千万别回到危机四伏的霍格·沃兹学校去。
Scene 2: When Harry enters his bedroom, the house elf Dobby is waiting for him who warns him that under no circumstances is he to return to Hogwarts, where a great danger is waiting for him.
场景二：礼拜天，女人和男人一起到街上买衣服，女人带男人不断流连于一家又一家的男装店里，看着琳琅满目的服装，想像着他穿上的甜蜜。
Scene Two: Man and woman go shopping together on Sunday and they linger in one men’s store and another, looking at the glittering array of clothes and imaging the sweetness in them.
场景二：礼拜天，女人和男人一起到街上买衣服，女人带男人不断流连于一家又一家的男装店里，看着琳琅满目的服装，想像着他穿上的甜蜜。
Scene Two: Man and woman go shopping together on Sunday and they linger in one men’s store and another, looking at the glittering array of clothes and imaging the sweetness in them.
第二幕包含了我所看过的最为可笑的场景之一。
Act II contained one of the funniest scenes I have ever witnessed.
在第二次迭代中，你为这些场景添加了复杂性—例如，你也许使缺陷能够在一个工作流中处理。
In the second iteration, you add complexity to these scenarios — for example, you might enable the defect to handle a workflow.
嵌套的聚合：如果场景是第二种模式中描述的基本批处理模式，但是重复元素本身包含重复元素，则此模式非常有用。
Nested aggregation: This pattern is useful if the scenario is the basic batch processing pattern described in the second pattern, but the repeating elements themselves contain repeating elements.
在第二个评估场景中，我们将查看系统在每个工作负载下的内存使用量。
In our second evaluation scenario, we looked at how much memory the system used at each of the workloads.
本文将重点讨论八个SOA解决方案场景中的第二个：服务连接性场景。
This article focuses on the second of the eight SOA solution scenarios: the Service Connectivity scenario.
在第3部分中讨论了第二种场景，该场景提供了一种服务，通过该服务客户和雇员能够跟踪各个包的状态。
The second scenario, which was covered in Part 3, provided a service with which customers and employees could track the status of an individual package.
在第二个订阅场景中，希思罗机场(LHR)显示其航班抵达和起飞的信息。
In the second subscription scenario, Heathrow airport (LHR) displays its arrival and departure information to airport patrons.
让我们切换到第二个场景，此场景介绍服务的请求-响应类型。
Let's switch to our second scenario, which covers a request-response type of service.
把场景营造得独一无二，在真实生活中永远不会发生。
Make the scene so unique that it could never happen in real life.
图4展示了一个更类似的场景——事务中的第二个查询需要访问与第一个查询相同的节点上的数据。
Figure 4 shows a more likely scenario — that the second query in the transaction needs to access data on the same node as the first query.
第二个出站标识映射场景使用了发送服务器端中的一个自定义登录模块。
The second outbound identity mapping scenario USES a custom login module on the sending server side.
第二个参数是场景结点，指定受碰撞检测影响的对象，在我们的例子中就是相机。
The second parameter is the scene node, which is the object, which is affected by collision detection, in our case it is the camera.
第二种场景下，尽管部署是分阶段进行的，所获得的价值也是分阶段的，客户却在一开始就遭致全部费用加诸一身。
In the second scenario, the customer incurs the total cost right at the start, although deployment would likely be phased, as would the value obtained.
第二个场景根据字符串创建一个反向文本索引。
The second scenario creates an inverted text index from strings.
我不认为这需要特别聪明的人，或者我，来判断第二个场景比第一个场景更容易实现。
I don't think it takes anyone extremely smart or me to know that the second of the two scenarios is likelier to occur.
第二个“高级”场景实在有所不该。
在第一个场景(第二个是场景6)中，由应用程序代码执行标识映射，而不使用和配置自定义登录模块。
In the first scenario (the second is scenario 6), identity mapping is performed from the application code, without using and configuring custom login modules.
第二个场景中使用批处理存储库。
第二种场景建立在第一种场景之上，用来演示如何根据所调用的操作应用中介策略。
The second scenario is based on the first and is used to show how mediation policies can be conditionally applied based on which operation is being called.
至少三分之二的实现人员同意发布场景。
At least two thirds of those implementers agree to have the scenario published.
本文将介绍如何构建一个自定义小部件，可在上述第二种场景中轻松使用这些更新数据源。
This article describes how you can build a custom widget that makes it easy to use these relational update feeds for the second type of scenario listed above.
图2所示的是第二种场景，它包含与服务提供者透视图相同的流程，该流程在其基础结构中也自由使用ltpa令牌。
The second scenario, shown in Figure 2, looks at the same flow from the perspective of the service provider, who also happens to make liberal use of LTPA tokens within their infrastructure.
图2所示的是第二种场景，它包含与服务提供者透视图相同的流程，该流程在其基础结构中也自由使用ltpa令牌。
The second scenario, shown in Figure 2, looks at the same flow from the perspective of the service provider, who also happens to make liberal use of LTPA tokens within their infrastructure.
应用推荐