Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support the production of Desktop Agent Bridging #453

Closed
Tracked by #481
lspiro-Tick42 opened this issue Sep 8, 2021 · 3 comments · Fixed by #860 or #968
Closed
Tracked by #481

Support the production of Desktop Agent Bridging #453

lspiro-Tick42 opened this issue Sep 8, 2021 · 3 comments · Fixed by #860 or #968
Labels
api FDC3 API Working Group Desktop Agent Bridging Desktop Agent Bridging Discussion Group enhancement New feature or request

Comments

@lspiro-Tick42
Copy link

Enhancement Request

Extend the FDC3 API's to improve support for producing bridges between FDC3 implementations aka Desktop Agents.

In this context an FDC3 Bridge would allow an application running on one Desktop Agent, to be able to integrate with FDC3 applications running on a second Desktop Agent for the same user.

The interop between applications running on different Desktop Agents aka Platforms would ideally cover

  • Channels
  • Intents
  • Application Launching

Use Case:

  1. A Client has two Desktop Agent environments running on their desktop and wants to be able to raise an intent from an application running on Desktop Agent 1 (say Glue42) and the intent is implemented on Desktop Agent2 (say OpenFin).

  2. A similar use case occurs `round User Selected channels, where a user wants to see applications running on the 'same channel' from the multiple desktop agents, synchronise on a common symbol.
    NB This assumes that from a user PoV a red channel on Platform is the same as a red channel on Platform 2.

  3. An existing platform, say a Terminal offers interop between its applications using its own (non FDC3) API's. It wants to allow applications running on other Platforms to interwork with apps running on the Terminal. This could be acheived by delivering a Bridge for whatever Platforms a user may be running.

Additional Information

If this use case is accepted we can imagine two implementations, either adding a few extra API methods (for which change requests will be added) or by defining a Desktop Agent to Agent interop bus/api. But our view of the agenet to agent API is that it is too big a change.

@lspiro-Tick42 lspiro-Tick42 added the enhancement New feature or request label Sep 8, 2021
@kriswest
Copy link
Contributor

Consense reach at #481 that this issue is within the FDC3 charter and that work should be undertaken to achieve it.
Possible approaches to be presented at SWG next meeting.

@kriswest
Copy link
Contributor

kriswest commented Dec 6, 2021

A discussion group is being started up to discuss and develop proposals to resolve this issue:

@saurabhguptanwm
Copy link

saurabhguptanwm commented Jan 12, 2022

Addditional Usecase

  1. A client has 2 monolithic application created in C# and wants to send a FDC3 Context or Intent from one app to another.

  2. A client with 2 machines has 1 monolithic applcation running on Machine 1 and Desktop Agent (say Finsemble) running on Machine 2 and client would like to exchange context or Intent with each other.

@finos finos locked and limited conversation to collaborators Jan 14, 2022
@kriswest kriswest converted this issue into discussion #544 Jan 14, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
api FDC3 API Working Group Desktop Agent Bridging Desktop Agent Bridging Discussion Group enhancement New feature or request
Projects
None yet
3 participants