0.5.1-canary.3

What's Changed

• [+] added encoding for documents into binary (#441) by @thorseraq
• [+] implemented storing of ID in items (#439) by @darkskygit
• [+] added a guide on how to write a new connector to the documentation (#432) by @darkskygit
• [+] updated the write implementation (#427) by @darkskygit
• [+] completed the apply update implementation (#430) by @forehalo
• [+] refactored the client sync functionality (#428) by @darkskygit
• [+] added read/write traits for raw CRDT types (#422) by @darkskygit
• [+] implemented the application of awareness update (#421) by @darkskygit
• [*] completed the codec unit test (#437) by @thorseraq
• [*] refactored the read/write ybinary (#435) by @forehalo
• [*] migrated the Octobase playground to the homepage (#419) by @thorseraq
• [*] fixed the issue of missing updates during full migration (#426) by @thorseraq

TLDR

In this update, we continue to develop our CRDT implementation (#430, #435) and have accomplished a full read-write flow for CRDT Item and Yjs Binary (#421, #422, #427, #428, #439, #441). Furthermore, we've written a guide on how to integrate OctoBase with any bi-directional communication protocol, available for community reference (#432). We've now replaced the original yrs implementation with the OctoBase sync in our affine cloud servers, which have been running stably for two weeks, showing perceptible improvements in stability.

Full Changelog: p20230516...p20230528