Plexus Interop 以元数据为中心的语言无关的桌面应用程序互操作性框架（plexus公司介绍）

Plexus Interop 以元数据为中心的语言无关的桌面应用程序互操作性框架（plexus公司介绍）

Overview

Plexus Interop is metadata-centric language-agnostic desktop app-to-app interoperability framework with extensible model for launching new instances of desktop Apps on demand.

The main goal of the framework is to enable development of extensible workflows connecting independent Apps developed in different technologies (.NET, Web, Java, Python etc) and passing context (structured data objects) between them.

Framework architecture is based around central broker providing hub-and-spoke connectivity between Apps and brokering strongly typed RPC-style calls between them. Broker has a connection to Application Lifecycle Manager which is capable of creating new instances of the Apps based on the their runtime-metadata (e.g. container type, launch command, params etc) defined in a registry.

Plexus Interop separates interoperability from the container, which provides notable advantages: different containers can be leveraged in the same workflow, launched applications residing outside of containers can participate in interop activities.

Raising an Issue

Please raise issues to the project mailing list plexus-interop@symphony.foundation issue tracker. Some people from project teams currently can't access build-in github issue tracker from corporate network.Please also tag the new issue with either "Bug" or "Enhancement".

Repository Overview

Plexus Interop repository consist of the following main sections:

desktop - Interop Broker, .NET Interop Client and sample apps implemented in C# using .NET Core 2.0.web - Web Interop Client and sample apps implemented in TypeScript.dsl - Protobuf and Plexus Interop grammar parsers, validators and code-generators implemented using Xtext framework.docs - documentation implemented in AsciiDoc format using Asciidoctor processor.protocol - definitions of Plexus Interop protocol messages in Protobuf format.samples - sample interop metadata.

Build/Install

All Plexus Interop components can be build using Gradle tool using the following single command:

gradlew build --console plain

Build produces artifacts into folder "bin".

Running Samples

After successfull build samples binaries will be located in bin directory.

Run .Net to Web interop example on Windows:

Documentation

To check out docs, visit https://symphonyoss.github.io/plexus-interop/.

Documentation project is located in folder 'docs'. We build documentation using AsciiDoc.

To render diagrams during the build you need to have graphviz installed on the machine.

Invoke the following command to run the documentation build:

gradlew -p docs --console plain

After successful build documentation is available via:

bin/docs/html5/index.html

Contributing

Please refer to Contribution guidelines for this project.

版权声明：本文内容由网络用户投稿，版权归原作者所有，本站不拥有其著作权，亦不承担相应法律责任。如果您发现本站中有涉嫌抄袭或描述失实的内容，请联系我们jiasou666@gmail.com 处理，核实后本网站将在24小时内删除侵权内容。