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
It is only now that games are slowly starting to pile up and match histories are starting to get longer in the browser. There is a fair amount of graphics in there (7 per game) so once you hit 50-200 or so it might actually get really slow beacuse you have several thousand graphics per page. Originally I thought you might be able to provide the full match history without any problems but I'm not so sure about that anymore.
Perhaps it would be better to preemptively implement page based browsing with about 20 games per page at this point already. Ultimately this should possibly be implemented in the API, too.
The text was updated successfully, but these errors were encountered:
It is only now that games are slowly starting to pile up and match histories are starting to get longer in the browser. There is a fair amount of graphics in there (7 per game) so once you hit 50-200 or so it might actually get really slow beacuse you have several thousand graphics per page. Originally I thought you might be able to provide the full match history without any problems but I'm not so sure about that anymore.
Perhaps it would be better to preemptively implement page based browsing with about 20 games per page at this point already. Ultimately this should possibly be implemented in the API, too.
The text was updated successfully, but these errors were encountered: