Page Comparison

...

As outlined during the meeting on 24 Jan 2019 , this is the proposed 2019 roadmap for Plexus Interop:

Q1 2019

API: Desktop Interop API documentation improvements (simplification) – Done
Support adoption of Plexus Interop implementation in other organizationsorganizations – Haven't been any, conversation with JP-Morgan
Add extension points allowing gathering runtime interop stats from Plexus Interop Broker for monitoring and analyticsanalytics – Done
API: Desktop Interop API ratification. V1.0.0 ratified. Continue to evolve. – Check with Leslie
Program confluence curationcuration – Ongoing
Review alignment with FDC3 standardsFDC³ standards – Not done. Focus has been on different implementation of container rather than API
Implementation of FDC³ API on Glue42/ Plexus – Still being worked through
API: extension to include Pub-Sub, and Context Channels, to API standard – Pull Request still outstanding

Plexus: Simplified JS Client API: add support for JSON encoding in addition to Protobuf, remove protobuf.js dependency from JS client and make code-generation optionaloptional – Merged with Node.JS broker
API: define API language bindings for .NET and Java – Not done, check with Leslie
Review alignment with FDC3 standardsFDC³ standards – Not done. Focus has been on different implementation of container rather than API

Plexus: Implement broker on Node.JS in addition to current .NET implementationimplementation – Incremental version delivered in H2, work in progress, being developed in the open. Want this to be a collaborative effort with other members of the programme.
Review alignment with FDC3 standardsFDC³ standards – Not done. Focus has been on different implementation of container rather than API. FDC3 API can run on top of Desktop Interop API

- implementation of FDC3 API on Glue42/ Plexus

- Language bindings for Desktop API Spec

- pub / sub support

- Positioning of the Plexus programme

- Put emphasis on a wider community engagement

...