blinkvorti.blogg.se - january 2023

One Container At least one of them Shared Object To store logic, If necessary, there can also be multiple Object.SharedObject You can have state, from DDS(Distributed data structures) Responsible for storage and management sharing. Ĭlient The end is divided into two parts They are the of management status Fluid Container and Responsible for the connection Sercive And pull up / establish Container Of Fluid Loader Containerįirst of all Container, Container It contains app The logic of data operation and the data itself. This picture clearly shows Fluid Client General structure of the end. So each of them client After receiving the data operation queue sent by the client, from client Do it yourself merge operation, It can independently and accurately reproduce the operation of other end-to-end data, It also reduces Server End overhead, This reduces the delay. ( The picture is from Fluid Official documents )įluid Data modification, deletion and other maintenance are expressed as data operations on data structures one by one (data ops), and server The client only does some simple processing, Do not perform data consolidation personally, such as : After the received data is operated, take a number to line up and broadcast it ( Of course, it will keep one for storage ). In order to minimize overhead and efficiency ,Fluid Simplify the design as much as possible server The logic of the end, Give Way client The client is more involved in maintaining the state :

Īs a user, you can use Fluid Provided interface binding event, Implement event monitoring, Data modification and other functions, When the data of one end is modified, Other end Fluid The corresponding event will be triggered, So as to realize the multi terminal synchronization of data. Stay Client There is something similar to a pile at the end ( There is no official mention of Stub Ha I think so myself ) Responsible for the maintenance of shared status and communication with Server End to end interaction, Shield the underlying implementation logic. Use Fluid Framework For development, The client architecture is roughly like this : Mircosoft Loop ( Not yet released, It looks like notion A kind of multi person collaborative double chain notes ) etc.

Mircosoft Whiteboard ( A drawing board that supports multi person collaboration ).

Īt present, Microsoft itself is based on Fluid The applications developed are : Separate synchronization logic from business logic development itself, Use a low latency framework, Can better focus on the client development itself. Use Fluid The data structure and interface provided, You can use shared data as you would local data, At the same time, the data will automatically maintain multi terminal synchronization, And the latency is low and the server load is small ( At least that's what they say ). A framework that can realize real-time synchronization of multi terminal shared data Learn from Fluid Framwork Official documents Fluid Framework Documentation brief introductionįluid Framework It is an open source project of Microsoft The front-end frame is irrelevant Framework for distributing and synchronizing shared state.

( Mengxin wrote an article for the first time Maybe the writing is not deep enough or the understanding is not in place.