You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/content/docs/client/event-iterator.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ for await (const event of iterator) {
49
49
If an error occurs during streaming, oRPC will attempt retries based on your configuration. It can retry multiple times until the specified limit is reached, after which the error will be thrown.
50
50
51
51
::: info
52
-
If you're using [RPCLink](/docs/client/rpc-link), you can customize the retry behavior [here](/docs/client/rpc-link#event-source-configuration).
52
+
If you're using [RPCLink](/docs/client/rpc-link), you can customize the retry behavior [here](/docs/client/rpc-link#event-iterator-configuration).
Copy file name to clipboardExpand all lines: apps/content/docs/client/rpc-link.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,22 +118,22 @@ const link = new RPCLink<ClientContext>({
118
118
You should disable event iterator retries when streaming results from a chatbot AI.
119
119
:::
120
120
121
-
## Event-Source Ping Interval
121
+
## Event Iterator Keep Alive
122
122
123
-
To keep EventSource connections alive (the mechanism behind [Event Iterator](/docs/event-iterator)), `RPCLink` periodically sends a ping comment to the server. You can configure this behavior using the following options:
123
+
To keep [Event Iterator](/docs/event-iterator) connections alive, `RPCLink` periodically sends a ping comment to the server. You can configure this behavior using the following options:
124
124
125
-
-`eventSourcePingEnabled` (default: `true`) – Enables or disables pings.
126
-
-`eventSourcePingInterval` (default: `5000`) – Time between pings (in milliseconds).
127
-
-`eventSourcePingContent` (default: `''`) – Custom content for ping messages.
125
+
-`eventIteratorKeepAliveEnabled` (default: `true`) – Enables or disables pings.
126
+
-`eventIteratorKeepAliveInterval` (default: `5000`) – Time between pings (in milliseconds).
127
+
-`eventIteratorKeepAliveComment` (default: `''`) – Custom content for ping messages.
These options for sending [Event Iterator](/docs/event-iterator) from client to the server, not from the server to client as used in [RPCHandler](/docs/rpc-handler#event-source-ping-interval) or [OpenAPIHandler](/docs/openapi/openapi-handler#event-source-ping-interval).
138
+
These options for sending [Event Iterator](/docs/event-iterator) from client to the server, not from the server to client as used in [RPCHandler](/docs/rpc-handler#event-iterator-keep-alive) or [OpenAPIHandler](/docs/openapi/openapi-handler#event-iterator-keep-alive).
To keep EventSource connections alive (the mechanism behind [Event Iterator](/docs/event-iterator)), `OpenAPIHandler` periodically sends a ping comment to the client. You can configure this behavior using the following options:
92
+
To keep [Event Iterator](/docs/event-iterator) connections alive, `OpenAPIHandler` periodically sends a ping comment to the client. You can configure this behavior using the following options:
93
93
94
-
-`eventSourcePingEnabled` (default: `true`) – Enables or disables pings.
95
-
-`eventSourcePingInterval` (default: `5000`) – Time between pings (in milliseconds).
96
-
-`eventSourcePingContent` (default: `''`) – Custom content for ping messages.
94
+
-`eventIteratorKeepAliveEnabled` (default: `true`) – Enables or disables pings.
95
+
-`eventIteratorKeepAliveInterval` (default: `5000`) – Time between pings (in milliseconds).
96
+
-`eventIteratorKeepAliveComment` (default: `''`) – Custom content for ping messages.
To keep EventSource connections alive (the mechanism behind [Event Iterator](/docs/event-iterator)), `RPCHandler` periodically sends a ping comment to the client. You can configure this behavior using the following options:
71
+
To keep [Event Iterator](/docs/event-iterator) connections alive, `RPCHandler` periodically sends a ping comment to the client. You can configure this behavior using the following options:
72
72
73
-
-`eventSourcePingEnabled` (default: `true`) – Enables or disables pings.
74
-
-`eventSourcePingInterval` (default: `5000`) – Time between pings (in milliseconds).
75
-
-`eventSourcePingContent` (default: `''`) – Custom content for ping messages.
73
+
-`eventIteratorKeepAliveEnabled` (default: `true`) – Enables or disables pings.
74
+
-`eventIteratorKeepAliveInterval` (default: `5000`) – Time between pings (in milliseconds).
75
+
-`eventIteratorKeepAliveComment` (default: `''`) – Custom content for ping comments.
0 commit comments