分布式应用程序的事件聚合器
我正在使用 Prism 实现一个应用程序。 该应用程序具有一些驻留在各种计算机或服务器上的分布式组件。为了与它们进行通信，我计划使用事件聚合器来实现消息传递服务。但在开始研究之前，我想澄清一些问题：
事件聚合器可以在分布式环境中使用吗？如果是 而不是如何定义消息所在的服务器或集线器 已发布或已订阅？
使用事件对应用程序的性能影响是什么 聚合器？我觉得它可以忽略不计，但我仍然想知道。
事件聚合器方法是否有利于未来的扩展 企业环境？
谢谢和问候，
阿什什·夏尔马
I am implementing an application using Prism.
The application has a few distributed components that resides on various machines or servers. In order to communicate them, I am planning to implement messaging service using Event Aggregator. But before I start working on that I would like to have a few clarifications:
Can Event Aggregator be used on a distributed environment. If yes
than how to define the server or hub where the message would be
published or subscribed?What is the performance impact on the applications using Event
Aggregator? I feel it is negligible but still I would like to know.Is Event Aggregator approach is good for future expansion in an
enterprise environment?
Thanks and Regards,
Ashish Sharma
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
PRISM 是客户端技术。因此，
EventAggregator因为它本身无法满足您的需要。这是模块之间以松耦合方式进行通信的机制。这不是关于不同客户之间的通信。对于你所需要的 - 我会研究 HTTP Polling Duplex
http://www.devproconnections.com /article/silverlight-40/using-http-polling-duplex-in-silverlight-applications
如果您在前端使用 PRISM - 您可以编写自己的服务并订阅/发布在进行服务器调用并接收返回响应时，来自该服务的 EventAggregator 事件。
PRISM is client-side technology. So,
EventAggregatoras it is won't do what you need. This is mechanism to communicate between modules in a loosely-coupled way. It is not about communicating between different clients.For what you need - I would look into HTTP Polling Duplex
http://www.devproconnections.com/article/silverlight-40/using-http-polling-duplex-in-silverlight-applications
If you use PRISM on front end - you can write your own service and subscribe/publish EventAggregator events from that service while making server calls and receiving responses back.