> On May 25, 2017, at 9:14 AM, Brezal Campio <[hidden email]> wrote:
> For a some function which is the following:
> - begin with request count at 0
> - check current request count
> - if current current is less than allowed requests
> - spin up a new process
> - way for some given time and reset count to 0
> This is a naive approach to rate limiting, but is there common terminology for something like this?
> I am interested in less naive approaches to rate limiting requests as well if anyone is willing to point in the right direction.
> erlang-questions mailing list
> [hidden email] > http://erlang.org/mailman/listinfo/erlang-questions