Gateway Rate Limit Clarification #5898
-
|
Please answer which one it is using the language defined #5844 (comment) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
|
it is per connection |
Beta Was this translation helpful? Give feedback.
-
|
Or 120 per each connection (which is per session)? |
Beta Was this translation helpful? Give feedback.
-
|
Per connection (which is not the same as session) |
Beta Was this translation helpful? Give feedback.
-
|
What's the difference? @MinnDevelopment |
Beta Was this translation helpful? Give feedback.
-
|
When you reconnect you can resume your existing session by passing a session_id in a resume payload. The connection is your websocket connection, and the session is what is attached to your session_id. So, if the rate-limit would be per session, that would imply that it continues into your resumed session after reconnecting, which is not true. |
Beta Was this translation helpful? Give feedback.
-
|
The definition provided is incorrect. |
Beta Was this translation helpful? Give feedback.
-
|
Connection vs. Session vs. Shard Definition: switchupcb/disgo#26 (comment) The confirmed rate limit is PER CONNECTION. Discord Employee Confirmation (@devsnek): #5898 (comment) |
Beta Was this translation helpful? Give feedback.
Connection vs. Session vs. Shard Definition: switchupcb/disgo#26 (comment)
Visual: switchupcb/disgo#26 (comment)
Test: switchupcb/disgo#26 (comment)
The confirmed rate limit is PER CONNECTION.
Discord Employee Confirmation (@devsnek): #5898 (comment)
Discord Employee Confirmation (@appellation): #5844 (comment)