From 39fdb1dbd7f043edb71de1fea72f10e0cc915a22 Mon Sep 17 00:00:00 2001 From: Ali Behjati Date: Thu, 22 Aug 2024 16:07:35 +0200 Subject: [PATCH] agent: update websocket docs --- .../price-feeds/publish-data/pyth-client-websocket-api.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/pages/price-feeds/publish-data/pyth-client-websocket-api.mdx b/pages/price-feeds/publish-data/pyth-client-websocket-api.mdx index 4b177deb..7ad62613 100644 --- a/pages/price-feeds/publish-data/pyth-client-websocket-api.mdx +++ b/pages/price-feeds/publish-data/pyth-client-websocket-api.mdx @@ -8,7 +8,8 @@ - [get_product](pyth-client-websocket-api.md#get_product) - [get_all_products](pyth-client-websocket-api.md#get_all_products) -Batch requests are processed in the order the requests appear within the batch. +Batch requests are processed in the order the requests appear within the batch. **Batching is highly recommended if the client sends +updates to over 50 price feeds.** ## get_product_list @@ -113,6 +114,9 @@ A successful response looks like: ## subscribe_price_sched +**This method can saturate the connection between the agent and the client. Please create a scheduler on the client side to avoid saturating the connection or +send price updates as soon as they are available.** + Subscribe to price update schedule. pyth-agent will notify the client whenever it should submit the next price for a subscribed symbol. The request looks like: