These are out of scope for this article, but you can find more information about them in the WS-RM specification.
这些协议消息超出了本文的讨论范围，您可以在 WS-RM规范 中了解关于它们的更多信息。
The authors made this change to ensure that the protocol enabled efficient resource reclamation on the part of the rm Destination for terminated rm Sequences.
作者作出此修改是为了确保对于终止的RM序列，在RM的目的地端能够进行有效的资源回收。
The RM must associate any changes to the application state with the transaction requesting the changes.
RM必须使对应用程序状态所做的任何更改与请求更改的事务相关联。
This optimization allows the endpoints to establish corresponding RM Sequences with a single message exchange pair.
这种优化允许端点通过一个单一的消息交换对创建响应的RM序列。
This important concept is crucial in understanding how WS-RM solves the problem.
这个重要的概念对理解WS - RM如何解决此问题非常关键。
This solution was rejected because it required a change to the normal WS-RM processing model.
由于需要对普通WS - RM处理模型进行更改，因此否决了此解决方案。
Notice this is not that different from how WS-RM uses empty response flows to send new SOAP envelopes to carry WS-RM acknowledgements.
请注意，这与现在 WS-RM使用空响应流发送包含 WS-RM确认信息的新SOAP信封的方式区别并不大。
Like these plan documents, a requirements management (RM) plan can provide tremendous benefit to a project.
跟这些计划文档一样，需求管理(RM)计划对项目有很大的好处。
In this case, the RM generally does most of the work to commit or roll back the transaction.
在这种情况下，RM通常执行提交或回滚事务所需的大部分工作。
The RM plan also describes the change management process so that everyone on the project will understand it.
RM计划还描述了变更管理流程，以使项目中的所有人都能理解它。
WS-RM has these same delivery assurance rules, but they are not part of the messages.
WS-RM 也有这些传送保证规则，但是并不是消息的一部分。
Almost all RM tools allow you to import existing requirements documents into the tool.
几乎所有的RM工具都允许你导入已有的需求文档。
You should now be able to configure WS-RM for your own applications and services.
您应该能够为您自己的应用程序和服务配置WS - RM。
Before we get into why the term "polling" isn't appropriate, we'll examine what the WS-RM specification defines.
在了解为何术语“轮询”并不合适前，我们将对WS - RM规范定义的内容进行分析。
This is where WS-RM will store messages and sequence state.
这是WS - RM存储消息和序列状态的地方。
Now let's take a look at what these messages look like using WS-RM.
现在让我们看一下使用WS - RM的话消息是什么样子。
WS-RM doesn't define any way for this sender to asynchronously receive ACKs.
WS - RM没有定义任何方法用来使发送方异步接收ack。
RM reveals that the request for retrieving a document was served within 0.2 seconds.
而RM 展示，处理检索文档的请求只花费了 0.2秒的时间。
An RM tool can help with this, too.
RM工具也能帮你完成这点。
These types of decisions are critical to a WS-RM endpoint's ability to do its job.
这种类型的决策对WS-RM端点完成其工作的能力非常关键。
RM tools allow you to easily create requirement types and give them attributes.
RM工具使你易于创建需求类型并赋予属性。
The RM plan also describes the documents you will use.
RM计划也描述了你要用到的文档。
Again, this would be quite a change to the normal WS-RM processing logic.
同样，这也会对普通WS - RM处理逻辑进行修改。
Later, the RM will update the actual disk blocks corresponding to the changed data.
之后，RM将根据所更改的数据更新实际的磁盘块。
You'll learn how how to configure this as part of the WS-RM binding shortly.
稍后您将了解如何配置它作为WS - RM绑定的一部分。
In many ways RM just plugs in with whatever other security model is already in place.
RM可有多种方法、以插件方式在其他安全模型中工作。
This method could benefit from the use of WS-RM.
此方法可以从WS - RM的使用中受益。
SOA-RM diagrams define element context groups like the one shown in Figure 1.
SOA-RM图定义了如图 1 所示的之类元素背景组。
Before working with the policy sets, let's look at the WS-RM properties you need to consider when defining an WS-RM policy type.
在使用策略集之前，我们先看一下定义WS - RM策略类型时需要考虑的WS - RM属性。
Before working with the policy sets, let's look at the WS-RM properties you need to consider when defining an WS-RM policy type.
在使用策略集之前，我们先看一下定义WS - RM策略类型时需要考虑的WS - RM属性。
应用推荐