Skip to content
Source
Sign inSign up

effect__experimental__EventLogServer.yaml

21 lines1.9 KB

1"@effect/experimental/EventLogServer#layerStorageMemory":
2 include: true
3 replacement: effect/eventlog/EventLogServerEncrypted#layerStorageMemory
4 note: Use the encrypted server memory storage layer; storage is now storeId- and session-aware.
5"@effect/experimental/EventLogServer#makeHandler":
6 replacement: effect/eventlog/EventLogServerEncrypted#layer + effect/rpc/RpcServer#layerProtocolSocketServer
7 note: Compose the encrypted server layer with the generic RPC socket server; there is no per-socket handler factory.
8"@effect/experimental/EventLogServer#makeHandlerHttp":
9 replacement: effect/eventlog/EventLogServerEncrypted#layer + effect/rpc/RpcServer#makeProtocolWithHttpEffectWebsocket
10 note: Use the returned httpEffect for upgrades and provide its protocol to the encrypted server layer.
11"@effect/experimental/EventLogServer#makeStorageMemory":
12 replacement: effect/eventlog/EventLogServerEncrypted#makeStorageMemory
13 note: Use the encrypted server memory storage constructor.
14"@effect/experimental/EventLogServer#Storage":
15 include: true
16 replacement: effect/eventlog/EventLogServerEncrypted#Storage
17 note: Use the storeId- and session-aware encrypted server Storage service. write and changes now operate on encrypted batches. write returns newly stored batches and skips a batch only when all its entry ids are already known. Custom storage must implement entrySequences to look up acknowledgements for skipped batches; each batch owns consecutive sequences starting at its sequence.
18"@effect/experimental/EventLogServer#PersistedEntry":
19 include: true
20 replacement: effect/eventlog/EventLogEncryption#EncryptedBatch
21 note: The per-entry class was removed; encrypted storage now accepts batch records containing entryIds, iv, and encryptedBatch. The class encoding helpers and entryIdString getter are not retained. Old per-entry ciphertext cannot be reused as an encrypted batch.