您可以为集群选择各种拓扑，例如每个服务器上的所有组件，或不同于流程容器的另一个节点上的消息引擎。
You can select various topologies for the cluster, such as all components on each server, or the messaging engine on a different node from the process container.
这篇文章的所有示例都使用Tomcat，但是可以很容易地把Tapestry用于您选择的其他servlet引擎。
Tomcat is used in the examples throughout this article, but you can easily use Tapestry with the servlet engine of your choice.
当SiBus被创建之后，仅仅在集群服务器其中一个上有一个活动的消息传递引擎，集群成员的所有服务请求都通过这个惟一的消息传递引擎选择路径发送。
When the SiBus is created, there is only one active messaging engine on one of the cluster servers, and all service requests to cluster members are routed through this single messaging engine.
象所有的MVC框架一样，微软最终通过ASP.NET路径选择引擎(Routing Engine)支持URL重写。
Like virtually all MVC frameworks, Microsoft finally supports URL rewriting via the ASP.NET Routing Engine.
象所有的MVC框架一样，微软最终通过ASP.NET路径选择引擎(Routing Engine)支持URL重写。
Like virtually all MVC frameworks, Microsoft finally supports URL rewriting via the ASP.NET Routing Engine.
应用推荐