Skip to content
guruofquality edited this page Sep 17, 2014 · 4 revisions

Roadmap and major features planned

Performance metrics

Metrics API

Expose additonal performance metrics through API. Currently we collect basic thoughput per port. More detail is needed, and short-run, long-run averages.

GUI Support

Expose live performance metrics into the graphical tool. Metrics could be displayed on the connection as a color or as a throughput number. Or add additional dock panels to enumerate and display metrics.

Language bindings

Java

Finish the Java-facing bindings so that Java can call into the Pothos Proxy API. And create java-style wrapper for Pothos::Block so the Block API best matches accepted coding practices in Java.

C#

C# bindings, both through mono and windows managed code.

GUI Improvements

Hierarchy design

Using the graphical tool to create topological hierarchies of processing blocks. Hierarchies can be included in top level designs, and deployed on available hosts. Modifications to hierarchies should cause re-evaluation of client topologies.

Block designer

Create a processing block in one of the supported languages. The block will be compiled and deployed on available hosts.

Wishlist

Topology redundancy

If a node in the network goes down, automatically redeploy the design on the next available node.

Flow constraints

Allow the user to describe an expected thoughput, or latency. Attempt to alter parameters to meet the constraint; such as modifying the buffer sizer per work() or applying high priority, or migrating hosts.