@fluidframework/core-interfaces
Advanced tools
The loader makes up the minimal kernel of the Fluid runtime. This kernel is responsible for providing access to Fluid storage as well as consensus over a quorum of clients.
Storage includes snapshots as well as the live and persisted operation stream.
The consensus system allows clients within the collaboration window to agree on document properties. One example of this is the npm package that should be loaded to process operations applied to the document.
The base document channel is 'owned' and run by the chaincode of the loader. It should be versioned and require a specific loader version.
The channels of the document run separate code as defined by the consensus field. It's possible we could further split this and have each channel have an independent code source and use the consensus to propagate it.
We could also possibly define a runtime code that gets executed independent of a chain - this would be for UI, etc...
A quorum proposal transitions between four possible states: propose, accept, reject, and commit.
A proposal begins in the propose state. The proposal is sent to the server and receives a sequence number which is used to uniquely identify it. Clients within the collaboration window accept the proposal by allowing their reference sequence number to go above the sequence number for the proposal. They reject it by submitting a reject message prior to sending a reference sequence number above the proposal number. Once the minimum sequence number goes above the sequence number for the proposal without any rejections it is considered accepted.
The proposal enters the commit state when the minimum sequence number goes above the sequence number at which it became accepted. In the commit state all subsequent messages are guaranteed to have been sent with knowledge of the proposal. Between the accept and commit state there may be messages with reference sequence numbers prior to the proposal being accepted.
FAQs
Fluid object interfaces
The npm package @fluidframework/core-interfaces receives a total of 12,254 weekly downloads. As such, @fluidframework/core-interfaces popularity was classified as popular.
We found that @fluidframework/core-interfaces demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
