As we have more and more keyboards and posts added, it's starting to become more important to only load a few of them at a time. In the first stage items of the main feed (posts and keyboards) should be loaded only a couple at a time (let's say 2-3 each) and more as the user scrolls down. This should be handled by using an offset value in the http request.
Currently the request below will return all the keyboards in the database ordered by the date they were added.
https://click-clack.cc:5000/api/keyboards/new/
This request would return the N keyboards starting with the Kth one, N being the page size and K the keyboards already loaded + 1. The original request without o specified would be equal to o=0
As we have more and more keyboards and posts added, it's starting to become more important to only load a few of them at a time. In the first stage items of the main feed (posts and keyboards) should be loaded only a couple at a time (let's say 2-3 each) and more as the user scrolls down. This should be handled by using an offset value in the http request.
Currently the request below will return all the keyboards in the database ordered by the date they were added.
This request would return the N keyboards starting with the Kth one, N being the page size and K the keyboards already loaded + 1. The original request without o specified would be equal to o=0
Later this will have to be implemented in the search results, the showroom and the market as well.