Typical designs for AD hoc networks have each end-node randomly select another node to pass its data onto.
自组网的经典设计方案是让每一个终端节点随机选择另外一个节点进行数据的传输。
All of these are transparent to you, as you still end up with a node that has the name you want.
所有这些对于您来说都是透明的，最终得到的是一个具有您所希望的名称的节点。
It is therefore connected to an end node.
因此它是连接到某个结束节点的。
End branches that release data with a stop node.
用一个停止节点终止分支并释放数据。
There is no mapping for an End node; they are ignored when exporting.
没有对结束节点的映射；在导出时将忽略它们。
A traversal can end at a single node, or at several nodes, or at no nodes at all.
遍历可以结束于单个节点、或多个节点，或者在根本没有节点处结束。
Connect data output of activities that are not released to the process output interface to an end or stop node to avoid dangling outputs.
将未释放到流程输出接口的的活动数据输出连接到某个结束或停止节点，以避免出现悬空输出。
A start node can only issue control flow, while stop and end nodes can also receive data flow.
开始节点只能发出控制流，而停止和结束节点还可以接收数据流。
The updated application is extracted to the install destination of the node at the end of synchronization operation.
在同步操作最后，会将已更新的应用程序提取到节点的安装目的地。
Very often, users are not aware of the global effect of a stop node and use it to end each of the individual branches of a process.
通常，用户不会察觉到停止节点的全局效果，而只是用它来终止某个流程中的每个单独的分支。
If you forgot to write expressions relative to the current node, you can easily end up with the wrong stylesheet, as in Listing 7.
如果忘记编写当前节点的相对表达式，那么最后就会得到如清单7所示的错误样式表。
In contrast, the end node only has a local effect; it only ends the single branch through which it was reached.
与之相反，结束节点只具有局部效果；它只会终止它到达的那个分支。
Without parallelism, the stop node has exactly the same effect as the end node, i.e., it ends the single branch through which it was reached.
在不存在并行的情况下，停止节点与结束节点的效果完全一样，也就是说，它将终止到达它的分支。
At the receiving end, there should be another intermediary node that can decompress and forward the message to its ultimate destination.
在接收端应该有另一个中介体节点，它可以对消息进行解压缩并将消息转发给最终目的地。
Connect to stop node to end this exercise.
连接到结束节点完成这个练习。
To recognise this line end as a delimiter, you can set the node to have a custom delimiter with a value of 15.
要将此行结束符识别为分隔符，可以设置节点使用值为15的自定义分隔符。
To accomplish the installation, you can add a script to the end of the GPFS installation to check whether the node is a storage server and install MSJ.
要安装它，需要在GPFS安装程序的末尾添加一个脚本来检查这个节点是否是一个存储服务器，然后再安装MS J。
Scenario 5 goes into more detail on the difference in the semantics of the end and stop node.
场景5将详细讨论结束和停止节点在语义方面的区别。
End handler waits until all child tokens are completed and then transitions to the next node.
End处理器等待所有的子令牌完成，然后transition到下个节点。
Using a stop node instead would not be a correct solution, because it would immediately end the whole process and prevent execution of Task 4.
此处如果换成停止节点将是一个错误的解决方案，因为它会立即终止整个流程，Task4将不会执行。
However, the process will not release its data in the simulation because the parallel branches involving Task 2 and Task 3 do not end with a stop node.
不过，在进行模拟时，该流程将不会释放它的数据，因为涉及Task2和Task3的分支不是以停止节点结束的。
The end node to which Task 3 previously connected is no longer needed.
现在已经不再需要Task3先前连接的结束节点了。
The compute node at the end of each Web service path would have to use a unique part of the Environment tree for its information.
每个Web服务路径末端的Compute节点可以使用environment树中一个唯一的部分来提供参考信息。
A special node to mark the end of the parse tree.
标志解析树结束的特殊节点。
The simulation in Business Modeler 6.0.2 requires that every path in the process model ends in a stop node, i.e., the end node should rarely be used.
在Business Modeler6.0.2 中进行的模拟，要求流程中的每条路径必须以一个停止节点终止，也就是说，结束节点是很少使用的。
Rejoin parallel branches with a join node and then place a single end or stop node, instead of ending parallel branches individually.
利用一个join节点重新联接并行分支，然后放置一个结束或停止节点，而不是分别结束每个并行分支。
When the delimiter is set to Broker System Line End, the node uses a line end sequence of bytes as the delimiter as appropriate for the platform on which the broker is being run.
当将分隔符设置为Broker系统行结束符时，节点将使用运行代理的平台上的相应行结束符字节序列作为分隔符。
When the delimiter is set to DOS or Unix line end, the node recognises a line end as the delimiter.
当将分隔符设置为dos或unix行结束符时，节点将行结束符识别为分隔符。
The third cycle starts in the fork preceding the end node, and leads back to the join following the decision.
第三个循环从结束节点之前的 fork中开始，并引回decision之后的 join。
The FileInput node detects records that end with a DOS or UNIX line end and propagates a message for each one that it finds.
FileInput节点检测以dos或unix行结束符结尾的记录，并为发现的每个记录传播一条消息。
应用推荐