-
Notifications
You must be signed in to change notification settings - Fork 132
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
FDC3 for Web Browsers Discussion group 29th Aug 2024 #1321
Labels
Comments
kriswest
added
help wanted
Extra attention is needed
meeting
FDC3 for Web Browsers
labels
Aug 28, 2024
Alex Dumitru / Citi |
David Hanson / Morgan Stanley 🚀 |
Rob Moffat / FINOS |
Johan Sandersson / Here (formerly OpenFin) 🎁 |
Giles Roadnight / Morgan Stanley |
Hugh Troeger / FactSet |
Kris West / interop.io 🚀 |
Closed
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Group overview
Group convened to discuss how to enable FDC3 use in a web browser, without the use of a browser extension (such as fdc3-desktop-agent or a container).
Issue: #896
Mailing list discussion: https://groups.google.com/a/finos.org/g/fdc3/c/jCvlLjokBLs
In a recent email on the FDC3 mailing list, @kriswest wrote:
... I also want to add that there is clearly significant interest in the community in enabling FDC3 use on the web. There is a strong use case in that it would enable better onboarding journeys with less drop-off (where you use an app on the web with others before adopting a desktop container or similar).
and:
But there are also additional challenges such as how to make the API available reliably without importing a proprietary module from a particular vendor into every app, how to deal with more than one implementation of API/Desktop Agent in the browser at once, how to do this reliably and securely within the browser sandbox etc.. Work needs to be done in the Standard to solve these issues and to make web browser use possible in a future FDC3 Standard version - which I believe is possible (and likely to involve using a vendor-agnostic FDC3 NPM module to detect and connect to API implementation(s)). However, we're going to need to do that work to enable the aforementioned API implementations to be compliant and if we fail to hold the line now on compliance with the current version of the FDC3 Standard, that may never happen.
Shared doc with current draft: https://tick42-my.sharepoint.com/:w:/g/personal/finsemble_datastore_interop_io/EZ0dfTCdRlJCnIF3C_1Oit0BF3fsXyvlMbisXp722DC9Kg?e=H2y7fn
Relevant issue tags
Current open issues that relate to the above concepts with the label:
Meeting Date
Thursday 29th August 2024 - 9am (US eastern timezone EDT) / 2pm (London, BST)
Zoom info
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.
Participation Requirements
Note: Meeting participants are expected to accept the terms of the FDC3 license (Community Specification License), understand the governance process and have a CLA in place.
Please click the following links at the start of the meeting if you have not done so previously.
Tracking Attendance
Note: Meeting participants are expected to add a comment to this GitHub issue in order that we can track attendance of FDC3 project meetings. Please do this at the start of the meeting.
Agenda
IntentMetadata.displayName
made optional as displayName is deprecated in Intent Standard: Make IntentMetadata.displayName optional as its deprecated #1280Minutes
Recent Changes to the proposal
Add heartbeat messages: App Liveness Check #1320
onClose
event on aMessagePort
(provides information on when garbage collection is occurring, which can be used to time certain attacks) which is preventing them from implementing it - unfortunate as that event would have been ideal to catch apps closingonbeforeunload
- this is not correct as thats a cancellable event and other handlers might cancel closeonunload
fits better, but is deprecated and unreliable - although we are aware of/planning for unreliability with the heartbeat messages..pagehide
wherepersisted == false
: App Liveness Check #1320 (comment)heartbeatResponseRequest
toheartbestAcknowledgment
frozen
state (chrome memorySaveer mode) as they may not be able to to respond to heartbeat messages until aresume
event. Again see the pagelifecycle API and notes on the issue App Liveness Check #1320 (comment)Question: Disposal/Teardown patterns in FDC3 #1263
Next steps
Action Items
heartbeatResponseRequest
toheartbestAcknowledgment
pagehide
when the event haspersisted == false
and an example of using the heartbeat messages (needs support for automated responses ingetAgent()
implementation - DA implementations can then use the heartbeat as they see fitRolled over and/or still in progress:
window.location.href
should be used by default, andwindow.location.href
should always have a matching origin to the specified URL.Untracked attendees
The text was updated successfully, but these errors were encountered: