fast forward remote changes

[jchris]

When a remote makes a sequence of changes in quick succession, they might come faster than the local can merge them.

Most of the time when this happens we can just skip to the most recent one, assuming they are a direct chain of parent/child relationships.

https://www.youtube.com/watch?v=j0X9fRf4cTk

The video shows the queue buildup we can fast foward.

Here is the code to where we can fast foward through parent child chains in the queue

fireproof/packages/fireproof/src/apply-head-queue.ts

Line 29 in de8c51f

await worker(task.newHead, task.prevHead, task.updates !== null)

[jchris]

Immediately after composing the above, I realized this is the correct concept but the wrong CRDT. It should be applied in the encrypted-blockstore module which means doing the work of making DbMeta track parents properly (currently hacked in as runtime state). see

fireproof/packages/encrypted-blockstore/src/loader.ts

Line 116 in de8c51f

async mergeDbMetaIntoClock(meta: DbMeta): Promise<void> {

for where it should be applied

[jchris]

Maybe we need to add parents array to this type, where the parents are links to the same type

fireproof/packages/connect/src/connection.ts

Line 139 in de8c51f

export type DbMetaEventBlock = EventBlock<{ dbMeta: Uint8Array }>

DbMetaEventBlock