Price showing for a lot may not be the truth, especially visible when the auction closes

[dblock]

A user was looking at an artwork page and when the auction closed he was still looking at a price at which they had placed a bid earlier. In fact what happened is that they got outbid, then because they had a max bid they actually got the lot at a different price.

When the auction closes, they need to be looking at a "lot sold".

Until the auction closes the price needs to update frequently.

[ashfurrow]

Sounds like a serious UX issue. Looping in @katarinabatina.

dB, how does this work on the web side of things? We poll the API every 60 seconds for updated data.

[ashfurrow]

Going to move this into the Long Term milestone since it's a bigger problem and we need to have UX and dev work done.

[dblock]

Web has the same problem, but users often don't expect to get new data without a page refresh on web (see artsy/force#2391). When you look at an artwork I think you want to poll a lot more frequently for that artwork's price. The server can definitely handle that if you properly implement If-Modified-Since/If-None-Match on the client.