我需要监控几个正在进行压力测试的系统。我想制作一个客户端-服务器 .NET(C#) 应用程序，它将 ping 系统以检查温度、内存使用情况等。
客户端将在启动时提供系统信息（cpu-mem-hdd 配置），然后它将经历多个基准测试/压力测试。服务器将跟踪执行的内容，并且还能够检测系统崩溃。我几乎拥有客户端的所有代码（已在系统上运行，使用 WMI）
我没有 .NET 远程处理或 WCF 的经验，但我认为这是学习它们的绝佳机会。
你会使用什么技术？
I need to monitor several systems going thru stress testing. I want to make a client-server .NET(C#) application that will ping the systems to check temperature, memory usage etc.
The client will provide system info (cpu-mem-hdd configuration) at start then it will undergo through several benchmark/stress tests. The server will keep track of what is been executed and also will be able to detect system crashes. I pretty much have all the code for the client (have been running on the system, using WMI)
I have no experience with .NET remoting nor WCF, but I think this is a great opportunity to learn them.
What technology would you use?
发布评论
评论（3）
WCF 旨在将 .net 远程处理与其他一些 Microsoft 技术统一起来。 WCF 为您提供了很大的灵活性，只需更改一些 .net 属性即可更改客户端-服务器体系结构的设计。
我建议您谨慎行事，并确保手头有一份良好的 WCF 参考资料。如果没有轮子，您将花费大量时间在泥浆中旋转。
WCF is meant to unify .net remoting with a handful of other Microsoft technologies. WCF gives you a lot of flexibility to change the design of your client-server architecture simply by changing a few .net attributes.
I recommend you proceed with caution and make sure you have a good WCF reference at hand. You will spend a lot of time spinning your wheels in the mud without one.
Snmp，可能基于http://www.snmpsharpnet.com/。
没有什么奇特、新颖和闪亮的东西，而是一个旨在用于您所描述的内容的协议。绝对会是我的第一选择。
如果这不是您的选择：对我来说，第二选择是 WCF，因为它可以在不同的平台上使用（将来您会更加灵活）。
Snmp, maybe based on http://www.snmpsharpnet.com/.
Nothing fancy, new and shiny, but a protocol that is meant to be used for exactly the stuff you describe. Would definitely be my first choice.
If that is not an option for you: Second choice for me would be WCF, because that can be used from different platforms (you are more flexible in the future).
我会选择服务巴士。
i will choose service bus.