Kris West

I think it worth clarifying that the case you point to only applies contexts already on the channels (presumably retrieved via `getCurrentContext`), as it is intended that you process context...

> I then start a new window, and connect it to the Red and Green channel, so this should show the same Instrument as the first window, but there is...

~Added a comment to #313 based on this discussion - there's currently no way to know a user added you to a channel and that you need to go retrieve...

Channels joined via the DesktopAgent *are* PubSub like - which should be clarified in the spec and documentation: https://github.com/finos/FDC3/issues/418 Nevertheless, the API only allows you to join them one at...

A Standards Working Group vote is needed on this issue; should it be updated and merged into the 2.0 scope or closed? Issue summary: - Allow joining multiple channels through...

@lspiro-Tick42 The proposal is to allow the join multiple channels via the `fdc3.joinChannel` function (joining a channel via the desktop agent). I think what you are referring to is retrieving...

@Qiana-Citi many thanks for your input and details of your use-case. > So far FDC3 doesn’t support multiple channels, so in order to satisfy this use-case, we had to create...

After the last SWG meeting (#459), and based on the informal votes received, it was decided to remove this issue from the FDC3 2.0 milestone - but not to close...

@Vivek-NatWest > * behaviour of `channel.getCurrentContext` in case both desktop agents have channel state for same context type but with different value for example channel1 in both have fdc3.instrument but...

> Does this mean `fdc3Ready `event would not be fired by desktop agent until its connected to bridge? What would happen if there is no bridge running? No, the bridging...