Documentation / @etherfold/browser / HotUpdateGeneration

Type Alias: HotUpdateGeneration<ABI, ProcessResultType, ProcessorConfig>

HotUpdateGeneration<ABI, ProcessResultType, ProcessorConfig> = object

Defined in: packages/browser/src/hotUpdate.ts:117

THE TWO FACTORIES A HOT UPDATE ARRIVES WITH, and deliberately nothing else.

createState is WHERE THIS GENERATION'S STATE LIVES and it must be its OWN: a successor re-folds the stream from the start into a store of its own while the incumbent goes on writing its own, and two generations sharing one databaseName are ONE store by IndexedDB's definition -- they would collide on the rows and on the sync cursor, and the writer claim would demote one of them. The factory is the application's because the storage decision is (ADR-0077).

There is NO processorIdentity, and its absence is the point. This arrival has no bytes to hash, so the identity is derived from the module's HANDLER SOURCES once createProcessor has returned (moduleProcessorIdentity). An app that could state one would be back on the author-declared identity ADR-0086 deletes, re-entering through the one door left open -- and it would be silent whenever it was wrong.

Type Parameters

ABI

ABI extends Abi

ProcessResultType

ProcessResultType

ProcessorConfig

ProcessorConfig = undefined

Properties

createProcessor

createProcessor: BrowserGenerationSpec<ABI, ProcessResultType, ProcessorConfig>["createProcessor"]

Defined in: packages/browser/src/hotUpdate.ts:119

---

createState

createState: BrowserGenerationSpec<ABI, ProcessResultType, ProcessorConfig>["createState"]

Defined in: packages/browser/src/hotUpdate.ts:118