Quote:
Originally Posted by BigRed75
You are literally the first person that I have seen in any of these threads who has raised that concern. Everyone else complains about having to page through a bunch of auctions for cards they already own just to find the few they don't, including the OP of this thread.
And hiding listings obviously doesn't solve that problem. You still have to click through pages of chaff just to find the wheat.
|
I mean, we're not going to get the latter; it would require the devs to completely rework the way the server fills the request in the first place or (and this is what Matt Arnold was saying and what I agree would not work) making repeated calls to the server. I'm proposing a half measure.
That being said, why not increase the take to, say, 50 or 100 or 500, only show the first 20, and then load pages on demand after that? The biggest bottleneck / drain on the server is going to be the API call itself; after that, the only way the load would actually increase from 20 to probably even 500 is if theres so much data coming down that you'd have to split it into multiple packets, and in turn the only thing that would really have that big of a cost in that regard are the pictures, which I think you can see are already lazy-loaded in. Maybe you'd have to mess with the client side image lazy loading strategy with the actual auction house screen but I think that'd be about it.
Sent from my SM-G950U using Tapatalk