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
Disclaimer: I don't know where the bottlenecks on your servers are and whether the request count or the amount of the processed and sent data is the bigger issue, but I'll put this suggestion out there anyways...
For the information that updates multiple times during the 5 minute cooldown of a normal api request it would be great to have an api that does not need to send a large, and slow 350 KB response which only updates every 5 minutes. A small 5 KB response that updates every 5-20 seconds would be much more usefull in those cases.
Here is an example response to show how such a small and fast response could look like:
This discussion was converted from issue #537 on May 02, 2022 22:06.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Disclaimer: I don't know where the bottlenecks on your servers are and whether the request count or the amount of the processed and sent data is the bigger issue, but I'll put this suggestion out there anyways...
For the information that updates multiple times during the 5 minute cooldown of a normal api request it would be great to have an api that does not need to send a large, and slow 350 KB response which only updates every 5 minutes. A small 5 KB response that updates every 5-20 seconds would be much more usefull in those cases.
Here is an example response to show how such a small and fast response could look like:
Beta Was this translation helpful? Give feedback.
All reactions