I've been working on a project [1] which uses a hypermedia directory protocol [2] to orchestrate Web Workers and WebRTC peers, much like Plan9 did with namespaces. It uses HTTP rather than 9P.
The stated goal is to allow Web interactions to be defined by content rather than the page environment. The approach is an SOA which can be configured by manipulating views of the links exported by Web APIs. Workers can then share the page environment through mediated access.
This particular project is at the head of about 2 years of previous work [3] [4] [5]. There have been some failed approaches, and WebRTC was a detour to get launched [6]. I feel confident that GIDE will solve some of the past problems, though I'm waiting to see if it can achieve all of its goals.
My Slate programming language was intended to feature a module linking protocol that would have an ELF-like layer to link against native C code. And then the idea was that the object-slot graph would mirror or integrate with the file system. But the project has languished a bit, and I need to start over (would be glad to partner with somebody to share ideas).
The stated goal is to allow Web interactions to be defined by content rather than the page environment. The approach is an SOA which can be configured by manipulating views of the links exported by Web APIs. Workers can then share the page environment through mediated access.
This particular project is at the head of about 2 years of previous work [3] [4] [5]. There have been some failed approaches, and WebRTC was a detour to get launched [6]. I feel confident that GIDE will solve some of the past problems, though I'm waiting to see if it can achieve all of its goals.
1 https://grimwire.com/local/#docs/api/agent.md 2 https://github.com/grimwire/ide 3 https://www.youtube.com/watch?v=CJLiAdYTDz8 4 https://www.youtube.com/watch?v=VK3KcoOnROA 5 https://www.youtube.com/watch?v=PR-DvCEy1vA 6 https://grimwire.net