8 releases (4 breaking)
|new 0.5.1||Jul 24, 2021|
|0.5.0||Jun 13, 2021|
|0.4.0||May 12, 2021|
|0.3.0||Jan 8, 2021|
|0.1.0||Oct 7, 2020|
#375 in Data structures
891 downloads per month
Used in 6 crates (via twilight-gateway)
Ratelimiting functionality for queueing new gateway sessions.
The gateway ratelimits how often clients can initialize new sessions. Instances of a queue are given to shards so that they can request to initialize a session.
Queue implementations must point to the same broker so that all shards across all clusters, processes, and other forms of multi-serviced applications, can work together and use the same ratelimiting source. That is, if you for example have two clusters in two different processes, then the two processes must use some unified form of ratelimiting: this can either mean using IPC to communicate ratelimiting or a broker.
Most users only need the
LocalQueue: it's a single-process queue for
smaller bots. Larger bots need the
LargeBotQueue, which supports
single-process Sharding for Very Large Bots through the use of bucket
Large bots, and smaller bots out of design, may need to implement their own
queue. The most common reason to need this is if you have clusters in
multiple processes. You'll need a broker to manage ratelimiting across them
all so a [
Queue] trait is provided that shards can use to make requests to