You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
After step 5, score and rank a bid has the following text:
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?
The text was updated successfully, but these errors were encountered: