pKineto
-
I’m not very knowledgeable about backend, so I’m worried.
-
Communication
-
https://qiita.com/suin/items/00dee8bac706a6d66862
- Please tell me the options for real-time communication between frontend and backend.
-
- The third option here seems good.
-
I’m thinking of using either Kubernetes or Cloud Functions to process and manipulate Firebase.
-
-
Cloud Functions vs Kubernetes Engine
-
-
The current pen synchronization system is not very smart, so I want to find a better solution.
- It should also be able to handle Kineto Whiteboard.
- For now, the worst part is the regular updates.
- It should be push-based instead of pull-based.
-
As for the improved specifications,
- Receive push notifications if there are any changes within the monitoring range in seconds.
- Monitor a wider range than the display range and increase the time resolution in the temporal direction compared to the regular update tempo.
-
Also, we need to decide on a protocol to make version upgrades easier.
-
The structure of Firebase Realtime Database is described below (this will be the master).
-
- devices: - - - : true - items: -
- type: {"sticky", "stroke", "vote"...} - frames: - : true - timeline: - - : true - frames - - itemUUID: - - deviceUDID:
- playingPoint: - : true - items: -
-
Note
- Each frame only contains the differences.
- The sum up to a certain point should be calculated by the client itself.
- (Otherwise, if past modifications occur, future data would also need to be changed.)
- However, sticky notes might be an exception.
-
Pseudo-synchronization: every 0.1 seconds
-
Synchronization: every 1 second