julian.kiedaischandClaude Opus 5.5
4b33e36580
From 16 KB a picture's or binary file's entry names its bytes by their SHA-256 instead of holding them; the bytes are on F, content-addressed (GET/POST /blobs with the session's grant, from the editor's origin, at most 16 MiB). A document's blob side says where they are: the editor's fetches and uploads, the room thread's asks F's main thread, and a start waits for the ones asked for; without a side everything stays in the document. Text stays Y.Text. A blob whose bytes are not there is never written back empty. A blob F has not got yet is asked for again a few times, and a running room reads late bytes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
17 lines
496 B
TypeScript
17 lines
496 B
TypeScript
// Public surface of the shared document.
|
|
export * from './blobs.js';
|
|
export * from './commands.js';
|
|
export * from './documentation.js';
|
|
export * from './fields.js';
|
|
export * from './files.js';
|
|
export * from './janitor.js';
|
|
export * from './projectDoc.js';
|
|
export * from './report.js';
|
|
export * from './settings.js';
|
|
export * from './simulation.js';
|
|
export * from './sheet.js';
|
|
export * from './snapshot.js';
|
|
export * from './values.js';
|
|
export * from './view.js';
|
|
export * from './software.js';
|