Kris West

Closed via the adoption of the .NET binding. However, other bindings are still desired!

Hi @Davidhanson90, Connection to one or more app directories is recommended (SHOULD) for implementations, but not required (MUST): > An FDC3 Standard compliant Desktop Agent implementation SHOULD: > > -...

As the use of a hosted appD is _recommended_ rather than _required_ (SHOULD rather than MUST), and there are many examples of DesktopAgents that use configuration files rather than appD...

Hi @amanjmd user channels are joined at runtime via the Desktop Agent API. The role of the app directory is simply to describe an app's capability of using those channels...

@amanjmd during the hackathon kickoff we recommended that implementations are first created in their own respository and submitted as part of the hackathon - I'd recommend doing that whether you...

Hi @amanjmd apologies for any delay here, @robmoffat and I have both had our heads in a big refactor of the FDC3 repository and implementation of FDC3 for Web Browsers...

Agreed, this would be a good time to get this done. There are at least two implementations to consider, based on different technologies. I believe @amanjmd's implementation is based on...

I don't think we've discussed this properly yet, added to tomorrows meeting agenda: - https://github.com/finos/FDC3/issues/1267

FYI Channel listener, intent listener and event listener subscriptions are all covered by the Listener object (and its `unsubscribe`() fn) returned by the relevant `add*Listener` function. We did do some...

Notes from [SWG meeting 22/08/24](https://github.com/finos/FDC3/issues/1317): > - There was some discussion of background to this issue (raised by @Davidhanson90), including how containers (the traditional focus of FDC3) haven't needed any...