diff --git a/README.md b/README.md index e1ddc8c9704b39caf238b313c861cd1c985f5fe5..d23ee1ba301dac8028b3cd78832bf382532d77be 100644 --- a/README.md +++ b/README.md @@ -2,9 +2,9 @@ This library builds upon the previous Reowolf 1.0 implementation, with the intention of incrementally moving towards Reowolf 2.0. The goals of Reowolf 2.0 are to provide a generalization of sockets for communication over the internet, to simplify the implementation of algorithms that require distributed consensus, and to have a clear delineation between protocol and data whenever information is transmitted over the internet. -The Reowolf 1.1 implementation has the main goal of extending the Protocol Description Language (PDL) to be more pragmatic. The language now supports `struct`, `enum` and `union` types, has support for basic ad-hoc polymorphism, supports basic pattern matching, and makes channels of communication specify the types of values they're transmitting. +The Reowolf 1.1 implementation had the main goal of extending the Protocol Description Language (PDL) to be more pragmatic. The language now supports `struct`, `enum` and `union` types, has support for basic ad-hoc polymorphism, supports basic pattern matching, and makes channels of communication specify the types of values they're transmitting. -Reowolf 1.2 will focus on replacing the centralized algorithm for consensus with a distributed one. The distributed implementation should reduce the overhead of synchronization and consensus, especially in the case where the communicating parties are governed by simple protocols. +The current Reowolf 1.2 implementation focused on replacing the centralized algorithm for consensus with a distributed one. No longer are synchronous regions fixed, but they are discovered during each round at runtime. Furthermore, the consensus algorithm was adapted to allow multiple firings of a port within a single synchronous round. The components that constitute a protocol now run on a user-specified number of threads, scheduled as needed to complete the protocol's behaviour. ## Compilation instructions