Reactive programming is a popular paradigm to program event-driven applications, and it is often proposed as a paradigm to write distributed applications. One such type of application is *prosumer* applications, which are distributed applications that both produce and consume many events. We analyse the problems that occur when using a reactive programming language or framework to implement prosumer applications. We find that the assumption of an open network, which means prosumers of various types spontaneously join and leave the network, can cause a lot of code complexity or run-time inefficiency. At the basis of these issues lies *acquaintance management*: the ability to discover prosumers as they join and leave the network, and correctly maintaining this state throughout the reactive program. Most existing reactive programming languages and frameworks have limited support for managing acquaintances, resulting in accidental complexity of the code or inefficient computations. In this paper we present acquaintance management for reactive programs. First, we design an *acquaintance discovery* mechanism to create a *flock* that automatically discovers prosumers on the network. An important aspect of flocks is their integration with reactive programs, such that a reactive program can correctly and efficiently maintain its state. To this end we design an *acquaintance maintenance* mechanism: a new type of operator for functional reactive programming languages that we call `deploy-*`. The `deploy-*` operator enables correct and efficient reactions to time-varying collections of discovered prosumers. The proposed mechanisms are implemented in a reactive programming language called Stella, which serves as a linguistic vehicle to demonstrate the ideas of our approach. Our implementation of acquaintance management results in computationally efficient and idiomatic reactive code. We evaluate our approach quantitatively via benchmarks that show that our implementation is efficient: computations will efficiently update whenever a new prosumer is discovered, or a connected prosumer is dropped. To evaluate the distributed capabilities of our prototype implementation, we implement a use-case that simulates the bike-sharing infrastructure of Brussels, and we run it on a Raspberry Pi cluster computer. We consider our work to be an important step to use functional reactive programming to build distributed systems for open networks, in other words, distributed reactive programs that involve many prosumer devices and sensors that spontaneously join and leave the network.
翻译:重新编程是编程事件驱动应用程序的流行范式, 并且常常被提议为写分配应用程序的典型。 此类应用类型是* passomer* 应用程序, 它们是分布式应用程序, 既产生又消耗许多事件。 我们分析使用反应式编程语言或框架来实施编程应用程序时出现的问题。 我们发现, 假设一个开放的网络, 意味着各种类型的编程者自发加入并离开网络, 可能会造成大量代码复杂性或运行时间效率低下。 在这些问题的基础上, “ 熟悉” 管理* : 在它们加入和离开网络时, 能够发现预产期者, 正确维护整个反应式程序。 多数现有的反应式编程语言和框架对于管理熟人来说支持有限, 导致代码的意外复杂或低效率计算。 首先, 我们设计一个“ 适度” 发现* 机制, 在网络上自动发现快速编程的编程* 。 一个重要的编程* 系统, 用来自动发现预算器在网络上 。 一个重要方面是它们与反应式程序整合, 使机变现的计算器能能能运行程序能够正常运行 运行程序能够正确运行。