Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Desktop Agent Bridging Discussion group 23rd Nov 2022 #862

Closed
8 of 10 tasks
kriswest opened this issue Nov 23, 2022 · 13 comments
Closed
8 of 10 tasks

Desktop Agent Bridging Discussion group 23rd Nov 2022 #862

kriswest opened this issue Nov 23, 2022 · 13 comments
Labels
Desktop Agent Bridging Desktop Agent Bridging Discussion Group help wanted Extra attention is needed indexed When a meeting attendance is being tracked meeting

Comments

@kriswest
Copy link
Contributor

kriswest commented Nov 23, 2022 •
edited
Loading

Group overview

Discussion group for developing proposals for producing bridges between FDC3 implementations (aka Desktop Agents), allowing applications running on one Desktop Agent, 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
  • Raising and resolving Intents
  • Launching Applications

Relevant issue tags

Meeting Date

Wednesday 23 Nov 2022 - 9am EST / 2pm GMT

WebEx info

More ways to join

  • Join by video system:
  • Join by phone
    • +1-415-655-0003 US Toll
    • +44-20319-88141 UK Toll
  • Access code: 2558 920 8729

Meeting notices

  • FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

  • All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

  • FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.

  • FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

  • A Discussion Group has no direct decision-making power regarding the FDC3 standard - rather it is intended that anything they propose or work on will result in proposals (via Github issues and PRs) for the Standards Working Group participants to consider and vote on for inclusion in the standard.

Agenda

Minutes

  • A participant asked if for details timeline under which bridging will make it into the Standard.

    • @kriswest We aim to get bridging into FDC3 2.1 and it should be usable immediately (pending implementations)
      • No set date yet for FDC3 2.1 - should be discussed in the next SWG meeting
      • The current proposal is very close to a final draft - it'll need breaking up into multiple files in the final PR, but this is just an editing job.
      • Some participants often request that new features are demonstrated in use before they are added - this isn't a requirement but may be worthwhile in this case.

  • An update on the status of the Backplane contribution was provided by @Vivek-NatWest

    • Contribution was accepted and Backplane is now part of FINOS
      • Implementation details and docs: https://backplane.finos.org
      • Currently implements the connection protocol (with channel state synchronization) and the broadcast message exchange - others to be added, but will also require implementation by Destkop Agents (channel integration can be emulated through an app running in the DA, but other functions require lower-level implementation work).
      • Call to participants to go to the repo (at https://github.com/finos/backplane) and have a look
      • Call for contributions to take the implementation forward (Documentation, Code and Spec contributions all welcome)
      • Multi-machine use cases supported through default implementation that reads config (from appsettings.json) - alternative implementations with full discovery services can also be used with Backplane (as will need to be the case for most institutions)
      • An introduction to the code samples, configurations and examples in the Backplane project was provided
        • .Net and JS clients included (which will ease implementation by DA vendors)
        • JS Client can be used without a desktop agent (in a browser) for testing purposes!
      • @kriswest Highlighted that problems encountered during implementation will likely be the best indicators of gaps in the spec.
    • @kriswest Current contribution works as a technological base for Desktop Agent Bridging and should be expanded and it is important for other participants to get involved to validate the spec and mitigate edge-cases in real-world functioning.

  • Desktop Agent Bridging Proposal

  • @kriswest The group needs to propose a compliance categorization for this new part of FDC3, i.e. whether bridging will be required or recommended for 2.1

    • A required addition may be difficult until it has been implemented by a number of Desktop Agents - however this is still an option is some implement it prior to 2.1 being finalized and adopted
    • It will be up to the firms wishing to adopt and use this addition to advocate for a requirement if they want one.

  • @Vivek-NatWest Asked about port range and how the port number increment should be done when attempting connection.

    • @kriswest This is covered in the connection protocol already (See 'Step 1. Connect to WebSocket': proceed linearly through ports attempt handshake, fail fast and cycle through, pause at end of range before retrying)
    • We will review the port range since 100 ports seems excessive and may have been an editing mistake, 10 ports seems adequate for the default range (which could be overridden by configuration. Connection attempts should as per spec -

  • @kriswest highlights again for the importance of community involvement in the review of message exchanges and mentioned the conformance goal aim for bridging

Action Items

  • @kriswest @tpina Replace ResultError.DesktopAgentDisconnected with BridgingError.AgentDisconnected
  • @kriswest @tpina Complete PrivateChannel message exchanges
  • ALL review completed message exchanges
  • ALL Review/test Backplane repository!

Untracked attendees

Full name Affiliation GitHub username
@kriswest kriswest added help wanted Extra attention is needed meeting Desktop Agent Bridging Desktop Agent Bridging Discussion Group labels Nov 23, 2022
@tpina
Copy link
Contributor

tpina commented Nov 23, 2022

Tiago Pina / Cosaic

@Julia-Ritter
Copy link
Contributor

Julia / FINOS

@kriswest
Copy link
Contributor Author

Kris Wes / Cosaic 🚀

@Vivek-NatWest
Copy link

Vivek / Natwest

@pierreneu
Copy link

Pierre Neu / Symphony

@manish-nwm
Copy link

Manish / NWM

@mistryvinay
Copy link
Contributor

Vinay Mistry / Symphony

@WatsonCIQ
Copy link
Contributor

Chris Watson / Cosaic 👋

@timjenkel
Copy link

Tim / Wellington

@robmoffat
Copy link
Member

Rob / FINOS

@openfin-johans
Copy link
Contributor

Johan Sandersson / OpenFin 🎁

@rfinter13
Copy link

Rose Finter / FactSet

@jgavronsky
Copy link

Jane / FINOS

@kriswest kriswest mentioned this issue Jan 23, 2023
Closed
11 tasks
@kriswest kriswest closed this as completed Feb 6, 2023
@github-actions github-actions bot added the indexed When a meeting attendance is being tracked label Feb 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Desktop Agent Bridging Desktop Agent Bridging Discussion Group help wanted Extra attention is needed indexed When a meeting attendance is being tracked meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests