Pagination and related hurdles

[tyler-sommer]

After a time, the industry jobs page becomes very long and slow. The app needs a way to paginate the data, which could prove interesting for the model API. Some of the API calls allow paging, but even if not it can be implemented at the database layer. The same will be true for the assets page.

I am considering refreshing industry jobs, assets, and blueprints on a regular basis in a background worker. The feature would be opt-in, so a settings page might be in order. That would also necessitate forming some kind of "user profile".

Pagination would also make necessary a separate endpoint for each type that returns paginated data.

Other things to consider:

• Possible to paginate in the grpc layer?
• Use react or the like for the browser end of things; go all-in on RESTish endpoints and lots of javascript.
  • Might even be possible to make the front-end consume grpc.

[tyler-sommer]

3b61c38 added pagination that I think can be generalized decently. It still requires all results be loaded from the database for each page, but without re-working the model in a total sort of way, I think it's going to have to look like this.