.stl 转为.vtk_Stl.Fusion与SignalR有何相似之处？

.stl 转为.vtk

Even though both libraries are targeting similar problems (they help to write real-time apps faster), they do this quite differently:

即使这两个库都针对类似的问题(它们有助于更快地编写实时应用程序)，但它们的执行方式却大不相同：

• SignalR offers an API helping to deliver server-side notifications to the clients (and vice versa). It’s ~ a layer above WebSockets,that helps your server-side code to track clients, group them, and send messages to either individual clients, a group of them, or all the clients connected to hub (~ SignalR server). Besides that, SignalR has clients written in several languages, and I guess they implement connection resilience and some of other must-have features any production app needs.

  SignalR 提供了一个API，可帮助向客户端传递服务器端通知(反之亦然) 。 它是WebSockets之上的〜层，可帮助您的服务器端代码跟踪客户端，对其进行分组并向单个客户端，一组客户端或连接到集线器(〜SignalR服务器)的所有客户端发送消息。 除此之外，SignalR还用多种语言编写了客户端，我想他们实现了连接弹性以及任何生产应用程序需要的其他一些必备功能。

• And Stl.Fusion, even though it also uses WebSockets, solves a very different problem: it lets you find out when a piece of data you requested earlier gets changed. Fusion’s main selling points are:

  而且，即使Stl.Fusion也使用WebSockets，它也解决了一个非常不同的问题： 它使您能够发现何时更改了您先前请求的数据 。 Fusion的主要卖点是：

  a) it largely automates this complex task by

  a)通过以下方式很大程度上自动化了这项复杂的任务

  tracking dependencies between such pieces of data

  跟踪这些数据之间的依赖关系

  b)

  b)

  it is capable of doing this even if the data you consume is remote — and that’s exactly what enables Fusion-based real-time UI to work. Fusion offers a “replica service” abstraction, which looks identical to a similar server-side service, but instead of computing the output of any of its methods locally, it invokes a remote counterpart that does this and wires up everything needed to invalidate the replica as soon as matchin