-
Notifications
You must be signed in to change notification settings - Fork 113
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
onAddIntentListener JSON Schema like PC.onAddContextListener #1171
Comments
No, not quite right. Raised intents should always be targetted at a specific DA and This means that the user experience for intent resolution is provided in the DA where the Hence, there is no need in bridging for an This is detailed in the first two paragraphs here: https://fdc3.finos.org/docs/next/agent-bridging/ref/raiseIntent If its not clear, I'm happy to make any content edits you suggest. |
Hi @kriswest, That is perfectly clear. What isn't quite so clear I guess is my thinking on this in the first place, so this is really helpful. Here's a scenario:
I can see that this is kind of "out-of-scope" for bridging, but it would nevertheless be very useful from protocol point of view, otherwise, in order to respond correctly, the DA would have to send something like a "findIntent" message to B to see if it responds to the intent before collating all the results to send back to A. |
@robmoffat are you conflating/thinking about briding and FDC3 for the web in parallel? That would make this more complex as I think those cases differ a fair bit. In the FDC3 for the Web (or indeed any normal single DA case), then the Desktop does know that B has added the intent listener, because it handled the call to add it. Assuming, that B supports multiple instance AND that its appD entry states that it supports the intent/context pair then the DA should return (for findIntent OR and intent resolver) [instance of B, start new B, start new C] and has all the info to do so. In the bridging case, then theres a couple of possible cases to explore:
The first case is the same as the regular FDC3 case - the DA handled the addIntentListener call and so knows about it. It collects options from the other DA via findIntent, combines with its own options (that include the instance of B) and show the result to the user. The second case (B is ont he remote DA) is handled by sending out This is far far simpler than attempting to maintain details of every instance being managed by every DA all the time, which is what you'd have to do if the was just going to know the answer (we'd have to share details on connection to bridge and on every launch/close, every add/unsubscribe of a listener, as opposed to just on a raised intent). However, I think you are thinking about the FDC3 for Web case. In that situation, you need to support a message from the app to the DA for What I think you are running into is that bridging doesn't have an |
Hi @kriswest , Yes, sorry. All of my questions about bridging are related to FDC3 for the web! Your last paragraph was the key one for me, thanks. I'll let you know of any others as I come across them. |
I believe we've settled this one (but will talk more offline), closing for now. |
Enhancement Request
I am guessing that at the moment, the design is that when an intent is raised, it is sent to every other desktop agent. However, it might be a good idea to have a message for the desktop agent to receive a message for when the app adds or removes an intent listener?
The text was updated successfully, but these errors were encountered: