Lightweight solution for the concurrent editing problem described at large in the concurrent editing notification sibling project
Although highly efficient, current approach is impractical for complex applications as lacks good encapsulation.
The solution leverages undocumented and possibly evolving PropertyDDS:
- internal API.
- serialization format.
- internal state transitions
For the same reason the solution lacks portability.
Needed dependencies
$ node --version
v16.13.1
$ npm --version
8.1.2
Using NVM for node version management
nvm use v16.13.1cd FluidPatterns
npm run clean
npm install --legacy-peer-deps
npm run buildTerminal 1
npx tinyliciousTerminal 2
cd FluidPatterns/apps/concurrent-editing-notification-light
npm startSuper simplified notification demonstration using a single workspace and the internal api, state transitions and serialization format of PropertyDDS. Because of the above identified shortcomings this exercise serves only to formulate the theoretical foundation for its own rejection and is not a complete blue/red dot instantiation.
Edit the above diagram.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This project may contain Microsoft trademarks or logos for Microsoft projects, products, or services. Use of these trademarks or logos must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
