C＃5.0异步/等待功能和Rx - 反应扩展 [英] C# 5.0 async/await feature and Rx - Reactive Extensions

问题描述

我想知道什么新的C＃5.0异步功能意味着接收 - 反应扩展？这似乎是不补发，但他们似乎重叠 - 任务和的IObservable

I am wondering what do the new C# 5.0 asynchronous features mean for Rx - Reactive Extensions? It seems to be not a replacement but they seem to overlap - Task and IObservable.

编辑：<一href=\"http://blogs.msdn.com/b/flaviencharlon/archive/2012/08/06/task-lt-t-gt-vs-iobservable-lt-t-gt-when-to-use-what.aspx\">Task VS的IObservable：时使用何种

推荐答案

检查也： TPL数据流概述关于TDF和Rx：

Check also: TPL Dataflow Overview about TDF and Rx:

细心的读者可能会注意到TPL数据流和无功扩展（RX），目前可从DevLabs原型网站下载之间有一些相似之处。 Rx为predominantly专注于协调和事件的组成与基于LINQ的API流，用于处理数据的IObservables提供了一套丰富的组合子。相比之下，TPL数据流专注于提供构建模块，消息传递和并行高吞吐量和低延时CPU和I / O密集​​型应用，同时还提供了开发数据如何缓存明确的控制和对系统运行。因此，Rx和TPL数据流，而潜在地30000英尺的水平视为同类，满足不同的需求。即便如此，TPL数据流和Rx提供一个更好的在一起的故事。

Astute readers may notice some similarities between TPL Dataflow and Reactive Extensions (Rx), currently available as a download from the DevLabs prototypes site. Rx is predominantly focused on coordination and composition of event streams with a LINQ-based API, providing a rich set of combinators for manipulating IObservables of data. In contrast, TPL Dataflow is focused on providing building blocks for message passing and parallelizing CPU- and I/O-intensive applications with high-throughput and low-latency, while also providing developers explicit control over how data is buffered and moves about the system. As such, Rx and TPL Dataflow, while potentially viewed as similar at a 30,000 foot level, address distinct needs. Even so, TPL Dataflow and Rx provide a better together story.

这篇关于C＃5.0异步/等待功能和Rx - 反应扩展的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！