In addition, SandeshaContext can be used to set various runtime parameters to the RM Source.
另外，SandeshaContext还可以用于为RM Source设置各个运行时参数。
According to the specification, it is a core requirement that the RM Source has an endpoint reference.
根据规范中的说明，一项核心要求就是RM Source要具有端点引用。
The following messaging scenario explains the sequence of invocations of different components in RM Source and RM Destination.
以下的消息传递场景说明了RM Source和 RM Destination中不同组件的调用序列。
The RM Source identifies the last message in a Sequence by including a LastMessage child element in the Sequence header block.
RM源通过在Sequence 头部区域中包含一个LastMessage子元素来标志序列中的最后一个消息。
These two storage managers, which are not shown in Figure 3, provide the required functionality for the RM Source and RM Destination utilizing the Queue.
这两个存储管理器(未在图3中显示)使用Queue为RM Source和RMDestination提供了所需的功能。
Further, because the Sequence/Expires element was an xsd:datetime, it raised concerns regarding the need to synchronize clocks for the RM Source and Destination endpoints.
进一步讲，因为Sequence/Expires元素是xsd:datetime 类型的，这就产生了需要同步RM源和目标端点的时钟同步问题。
The RM Source MUST have an endpoint reference that uniquely identifies the RM Destination endpoint; correlations across messages addressed to the unique endpoint MUST be meaningful.
RM Source必须具有唯一标识RMdestination端点的端点引用；以此唯一端点为目标地址的消息间的关联必须有意义。
If the client invokes a web service with the IN-ONLY operation, then the sequence of invocations in both RM Source and RM Destination will be subsets of the sequences, as shown in Figure 7 above.
如果客户机使用in - ONLY操作调用Web服务，则RM Source和RMDestination中的调用序列都将为图7中所示的序列的子集。
The proposed model USES two EPMs, namely reliable Messaging (RM) Source and RM Destination, to handle the reliable delivery of messages.
所建议的模型使用了两个EPM，即可靠消息传递(RM)Source和RMDestination，用于处理消息的可靠传递。
The proposed model USES two EPMs, namely reliable Messaging (RM) Source and RM Destination, to handle the reliable delivery of messages.
所建议的模型使用了两个EPM，即可靠消息传递(RM)Source和RMDestination，用于处理消息的可靠传递。
应用推荐