Query: Recently, Microsoft unveiled the Fluid-Framework on GitHub. What are the steps to replace Signal-R with Microsoft's Fluid-Framework and what are the main differences?
Scenario: It appears that Fluid supports collaboration
and data synchronization for tools like Mermaid diagrams and Flowcharts
, which is a key use case. However, when attempting to switch from Signal-R
to Fluid-Framework
, the lack of documentation and guidance became evident.
Some points of confusion that require clarification:
The absence of clear details on the client-server connection is puzzling. For instance, configuring
in the Action/API signature is challenging without strongly typed examples.data sync frequency, fallback storage, custom claims within the container, port information, attribute binding
Requesting more robust server-side wiring examples.import { DataObject, DataObjectFactory } from "@fluidframework/aqueduct";
Fluid Container: Obtaining
Transition
orQuery information
for the active nodes' state and next nodes from the mermaid chart is unclear. How can this be achieved?
Difficulties due to lack of documentation https://i.sstatic.net/a83Hz.png