1"@effect/experimental/EventLogRemote#Ack":
2 replacement: none
3 note: A write acknowledgement is now the void success of EventLogMessage.WriteSingleRpc or WriteChunkedRpc.
4"@effect/experimental/EventLogRemote#Changes":
5 replacement: effect/eventlog/EventLogMessage#ChangesRpc
6 note: ChangesRpc replaces the separate request and response models with one streaming RPC.
7"@effect/experimental/EventLogRemote#decodeRequest":
8 replacement: effect/eventlog/EventLogMessage#EventLogRemoteRpcs
9 note: Generic RPC framing and RpcSerialization.layerSchemaBinary replace the module-specific request decoder.
10"@effect/experimental/EventLogRemote#decodeResponse":
11 replacement: effect/eventlog/EventLogMessage#EventLogRemoteRpcs
12 note: Generic RPC framing and RpcSerialization.layerSchemaBinary replace the module-specific response decoder.
13"@effect/experimental/EventLogRemote#encodeRequest":
14 replacement: effect/eventlog/EventLogMessage#EventLogRemoteRpcs
15 note: Generic RPC framing and RpcSerialization.layerSchemaBinary replace the module-specific request encoder.
16"@effect/experimental/EventLogRemote#encodeResponse":
17 replacement: effect/eventlog/EventLogMessage#EventLogRemoteRpcs
18 note: Generic RPC framing and RpcSerialization.layerSchemaBinary replace the module-specific response encoder.
19"@effect/experimental/EventLogRemote#EventLogRemote":
20 replacement: effect/eventlog/EventLogRemote#EventLogRemote
21 note: Use the v4 Context.Service; methods now take storeId-aware options.
22"@effect/experimental/EventLogRemote#fromSocket":
23 replacement: effect/eventlog/EventLogRemote#makeEncrypted + effect/rpc/RpcClient#makeProtocolSocket
24 note: Construct the encrypted remote separately from its generic RPC socket protocol.
25"@effect/experimental/EventLogRemote#Hello":
26 replacement: effect/eventlog/EventLogMessage#HelloResponse
27 note: HelloResponse replaces Hello and includes the v4 authentication challenge; HelloRpc defines the endpoint.
28"@effect/experimental/EventLogRemote#layerWebSocket":
29 replacement: effect/eventlog/EventLogRemote#layerEncrypted + effect/rpc/RpcClient#layerProtocolSocket
30 note: Compose the encrypted remote with the generic socket protocol, SchemaBinary serialization, and a Socket provider.
31"@effect/experimental/EventLogRemote#layerWebSocketBrowser":
32 replacement: effect/eventlog/EventLogRemote#layerEncrypted + effect/rpc/RpcClient#layerProtocolSocket + @effect/platform-browser/BrowserSocket#layerWebSocket
33 note: Compose the encrypted remote and generic RPC socket protocol with the browser WebSocket layer.
34"@effect/experimental/EventLogRemote#Pong":
35 replacement: none
36 note: The event-log Pong model was removed; heartbeats belong to the generic RPC socket protocol.
37"@effect/experimental/EventLogRemote#ProtocolRequest":
38 replacement: effect/eventlog/EventLogMessage#EventLogRemoteRpcs
39 note: EventLogRemoteRpcs and generic RPC serialization replace the old protocol request union.
40"@effect/experimental/EventLogRemote#ProtocolRequestMsgPack":
41 replacement: effect/rpc/RpcSerialization#layerSchemaBinary
42 note: Use the generic SchemaBinary RPC serialization layer instead of a request-specific schema.
43"@effect/experimental/EventLogRemote#ProtocolResponse":
44 replacement: effect/eventlog/EventLogMessage#EventLogRemoteRpcs
45 note: EventLogRemoteRpcs and generic RPC serialization replace the old protocol response union.
46"@effect/experimental/EventLogRemote#ProtocolResponseMsgPack":
47 replacement: effect/rpc/RpcSerialization#layerSchemaBinary
48 note: Use the generic SchemaBinary RPC serialization layer instead of a response-specific schema.
49"@effect/experimental/EventLogRemote#RemoteAdditions":
50 replacement: none
51 note: This unused protocol model has no v4 counterpart.
52"@effect/experimental/EventLogRemote#RequestChanges":
53 replacement: effect/eventlog/EventLogMessage#ChangesRpc
54 note: ChangesRpc replaces the separate request model with one streaming RPC.
55"@effect/experimental/EventLogRemote#StopChanges":
56 replacement: none
57 note: Interrupt the ChangesRpc stream instead of sending a StopChanges message.