Change Details

>>! In T236386#5716715, @Ottomata wrote: >> Is /v1/events plural with the intention that eventually EventGate will support batches of events in the same request? > > It does support that, just POST an array. It's really cool that this capability exists! Especially for mobile clients (where it could mean waking up the radio fewer times) and for `onUnload` (where we might want to flush the queue of logged events in a single go to make the page unload faster, rather than one at a time which negatively impacts next page load). We should look deeper into it, make sure we have an OK from #analytics to utilize it and that the pipeline is fully equipped to handle batches, and figure out an optimal batch size. If we end up doing this we want to get the benefit of bundling up several events into one request, but we wouldn't want to make the payload too heavy for cellular networks.

>>! In T236386#5716715, @Ottomata wrote: >> Is /v1/events plural with the intention that eventually EventGate will support batches of events in the same request? > > It does support that, just POST an array. It's really cool that this capability technically exists! This would be particularly useful for - mobile clients where it could mean waking up the radio fewer times, and - `onUnload` where we might want to flush the queue of logged events in a single go to make the page unload faster, rather than one at a time which negatively impacts next page load We should look deeper into it, make sure we have an OK from #analytics to utilize it and that the pipeline is fully equipped to handle batches, and figure out an optimal batch size. If we end up doing this we want to get the benefit of bundling up several events into one request, but we wouldn't want to make the payload too heavy for cellular networks and slow connections in general.

>>! In T236386#5716715, @Ottomata wrote: >> Is /v1/events plural with the intention that eventually EventGate will support batches of events in the same request? > > It does support that, just POST an array. It's really cool that this capability technically exists! This would be particularly useful for - mobile clients where it could mean waking up the radio fewer times, Especially for mobile clients (where it could mean waking up the radio fewer times) and forand - `onUnload` (where we might want to flush the queue of logged events in a single go to make the page unload faster, rather than one at a time which negatively impacts next page load). We should look deeper into it, make sure we have an OK from #analytics to utilize it and that the pipeline is fully equipped to handle batches, and figure out an optimal batch size. If we end up doing this we want to get the benefit of bundling up several events into one request, but we wouldn't want to make the payload too heavy for cellular networks and slow connections in general.