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: docs/reference/types/subscription.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,6 +105,8 @@ nav_order: 3
105
105
|`firstEvent`| Whether your application would like to receive events from the 'oldest' event emitted by your FireFly node (from the beginning of time), or the 'newest' event (from now), or a specific event sequence. Default is 'newest' |`SubOptsFirstEvent`|
106
106
|`readAhead`| The number of events to stream ahead to your application, while waiting for confirmation of consumption of those events. At least once delivery semantics are used in FireFly, so if your application crashes/reconnects this is the maximum number of events you would expect to be redelivered after it restarts |`uint16`|
107
107
|`withData`| Whether message events delivered over the subscription, should be packaged with the full data of those messages in-line as part of the event JSON payload. Or if the application should make separate REST calls to download that data. May not be supported on some transports. |`bool`|
108
+
|`batch`| Events are delivered in batches in an ordered array. The batch size is capped to the readAhead limit. The event payload is always an array even if there is a single event in the batch. Commonly used with Webhooks to allow events to be delivered and acknowledged in batches. |`bool`|
109
+
|`batchTimeout`| When batching is enabled, the optional timeout to send events even when the batch hasn't filled. |`string`|
108
110
|`fastack`| Webhooks only: When true the event will be acknowledged before the webhook is invoked, allowing parallel invocations |`bool`|
109
111
|`url`| Webhooks only: HTTP url to invoke. Can be relative if a base URL is set in the webhook plugin config |`string`|
110
112
|`method`| Webhooks only: HTTP method to invoke. Default=POST |`string`|
@@ -148,7 +150,7 @@ nav_order: 3
148
150
|`requestTimeout`| The max duration to hold a TLS handshake alive |`string`|
149
151
|`maxIdleConns`| The max number of idle connections to hold pooled |`int`|
150
152
|`idleTimeout`| The max duration to hold a HTTP keepalive connection between calls |`string`|
151
-
|`connectionTimeout`||`string`|
153
+
|`connectionTimeout`|The maximum amount of time that a connection is allowed to remain with no data transmitted.|`string`|
152
154
|`expectContinueTimeout`| See [ExpectContinueTimeout in the Go docs](https://pkg.go.dev/net/http#Transport)|`string`|
Copy file name to clipboardExpand all lines: docs/reference/types/wsstart.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,6 +96,8 @@ nav_order: 23
96
96
|`firstEvent`| Whether your application would like to receive events from the 'oldest' event emitted by your FireFly node (from the beginning of time), or the 'newest' event (from now), or a specific event sequence. Default is 'newest' |`SubOptsFirstEvent`|
97
97
|`readAhead`| The number of events to stream ahead to your application, while waiting for confirmation of consumption of those events. At least once delivery semantics are used in FireFly, so if your application crashes/reconnects this is the maximum number of events you would expect to be redelivered after it restarts |`uint16`|
98
98
|`withData`| Whether message events delivered over the subscription, should be packaged with the full data of those messages in-line as part of the event JSON payload. Or if the application should make separate REST calls to download that data. May not be supported on some transports. |`bool`|
99
+
|`batch`| Events are delivered in batches in an ordered array. The batch size is capped to the readAhead limit. The event payload is always an array even if there is a single event in the batch. Commonly used with Webhooks to allow events to be delivered and acknowledged in batches. |`bool`|
100
+
|`batchTimeout`| When batching is enabled, the optional timeout to send events even when the batch hasn't filled. |`string`|
99
101
|`fastack`| Webhooks only: When true the event will be acknowledged before the webhook is invoked, allowing parallel invocations |`bool`|
100
102
|`url`| Webhooks only: HTTP url to invoke. Can be relative if a base URL is set in the webhook plugin config |`string`|
101
103
|`method`| Webhooks only: HTTP method to invoke. Default=POST |`string`|
@@ -139,7 +141,7 @@ nav_order: 23
139
141
|`requestTimeout`| The max duration to hold a TLS handshake alive |`string`|
140
142
|`maxIdleConns`| The max number of idle connections to hold pooled |`int`|
141
143
|`idleTimeout`| The max duration to hold a HTTP keepalive connection between calls |`string`|
142
-
|`connectionTimeout`||`string`|
144
+
|`connectionTimeout`|The maximum amount of time that a connection is allowed to remain with no data transmitted.|`string`|
143
145
|`expectContinueTimeout`| See [ExpectContinueTimeout in the Go docs](https://pkg.go.dev/net/http#Transport)|`string`|
0 commit comments