Closed headerbidding closed 5 years ago
@headerbidding In 0.x all calls to requestBids were queued so at a time only one auction could run. Subsequent calls to requestBids would have to wait for previous auction to finish. With concurrent auction we removed this and allowed each auction to start as soon as requestBids is executed.
pbjs.requestBids(options1) // first auction
pbjs.requestBids(options2) // second auction
In 0.x second auction would be queued if first is not finished.
In >=1.0 both auction will start at the same time in parallel.
Hmmm. I thought there is just one auction for each ad and the highest bidder wins.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I still dont understand
I thought there is just one auction for each ad and the highest bidder wins.
There is just one auction per adunit. But there are use cases like infinite scroll where there's a series of calls to pbjs.requestBids()
Concurrent auction
means that subsequent calls to requestBids don't have to wait for their predecessors. So the auction #4 above can start before #3 completes.
Thank you. Now I got it 👍 -)
Cool
Type of issue
Question: Can someone explain in simpler terms (and with an example) what "concurrent auction" means?
Ref: https://gist.github.com/mkendall07/3dd690e7f624b61cb364fbf8a4ba8dbb