Kris West
Kris West
> It also underscores that there isn't anything missing from the standard to solve this problem. That is not the case @nkolba - it demonstrates that the problem, of establishing...
> As discussed in the standards meeting last week, it may helpful to split > this (and the previous email thread) into three separate topics: > > - Whether 1.2...
Great summary @novavi
At the last FDC3 Standards Working Group meeting (#899) it was resolved that a discussion group should be set up to discuss what changes need to be made to how...
Hi, > - the *window.fdc3* requirement is the only clearly identified issue > with the spec relating to FDC3 in browser > > Like @novavi, I heard no clearly articulated...
@api-forever > Note that the client-side integration with an IFRAME requires the ability > of the application to communicate its content height to the parent window > which hosts the...
Thanks Nick. That seems like a reasonable focus for the next meeting's agenda, see you there.
>Of course it's worth noting that for a local browser-based app to interop with a local desktop container or a remote (e.g. Citrix-based) container, then cloud-based interop is still absolutely...
@novavi just one item to pick up here: >This is because although many DA bridging scenarios will involve two different tech stacks or environments (which therefore require a cloud-based WebSockets...
Kris West / interop.io 🚀