Client defintion

[NoamFe]

is a client something that is pre-determined? meaning the idea is that there will be some configuration for a client?
something like:
clientX:
{
resource1: Rule A,
resource2: Rul A + Rule B
},
clientY:
{
resource1: Rule B,
resource2: Rul A + Rule B
}

[rgarf81]

In this exercise, the client would be a user making a request. So you would configure your resources to have some combination of rate limit(s), and track client requests. Nothing to configure per client.

[NoamFe]

So client is not a known system that you pre configured to have those rules? So a user is just any random user that is making an http request?

…

On Thu, Nov 14, 2024, 6:26 PM Ryan Garfield ***@***.***> wrote: In this exercise, the client would be a user making a request. So you would configure your resources to have some combination of rate limit(s), and track client requests. Nothing to configure *per client*. — Reply to this email directly, view it on GitHub <#253 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACYCQ65RQYZTUHDZGHUZQ732AU5SJAVCNFSM6AAAAABRUIJGCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZXGY4DMMRSGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[rgarf81]

A user accessing a known system, like a FE application or mobile app calling the API. These known systems will not know their rules, just have access to the API, where each endpoint can be configured to have rate limits on the user making the request.

[NoamFe]

Ok got it. So rules are strictly resource based and not client. Meaning if a rule exists on let's say GetPicture resource, that rule applies to all clients calling that resource. Am I correct?

…

On Thu, Nov 14, 2024, 6:53 PM Ryan Garfield ***@***.***> wrote: A user accessing a known system, like a FE application or mobile app calling the API. These known systems will not know their rules, just have access to the API, where each endpoint can be configured to have rate limits on the user making the request. — Reply to this email directly, view it on GitHub <#253 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACYCQ66S6HRQ2Y7FQYIAVOD2AVA2LAVCNFSM6AAAAABRUIJGCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZXG4ZTAMBQHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[rgarf81]

Correct

[NoamFe]

Thank you for clarifying. This is what I was thinking initially but started to doubt myself 😕

…

On Thu, Nov 14, 2024, 6:59 PM Ryan Garfield ***@***.***> wrote: Correct — Reply to this email directly, view it on GitHub <#253 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACYCQ62T7CA5URLGSHEKJUT2AVBQLAVCNFSM6AAAAABRUIJGCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZXG4ZTMNBRGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>