Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Score and rank a bid request batching #670

Open
domfarolino opened this issue Jun 26, 2023 · 0 comments
Open

Score and rank a bid request batching #670

domfarolino opened this issue Jun 26, 2023 · 0 comments
Labels
spec Relates to the spec

Comments

@domfarolino
Copy link
Collaborator

After step 5, score and rank a bid has the following text:

Implementations may batch requests by collecting render URLs and ad component render URLs from multiple invocations of score and rank a bid and passing them all to a single invocation of building trusted scoring signals url -- the network response has to be parsed to pull out the pieces relevant to each evaluation of a scoring script.

On the surface it seems like this optional "may" is allowing for a pretty substantive change in behavior that isn't totally clear. How would this actually impact the flow of this algorithm? Would multiple subsequent invocations of "score and rank a bid" build URLs and stop short of sending the request? Which one would finally send the request? The alternative flow that the "may" offers is too vague to follow, and its web-visible implications are not clear. Can we either remove this or specify more rigorously what this is trying to provide?

Furthermore the motivation of this isn't clear: do implementations actually do this?

@domfarolino domfarolino added the spec Relates to the spec label Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec Relates to the spec
Projects
None yet
Development

No branches or pull requests

1 participant