You can feed Doofinder data directly via API or allow Doofinder to read the data from a URL.
This way, URLs can point to already generated URLs (so they’re basically downloads), or to server endpoints that dynamically return the most up-to-date data directly from the database. Such endpoints can be expensive in terms of resources. Therefore, Doofinder splits the download into multiple requests to maintain performance by enabling feed pagination.
Pagination, in this case, refers to the ordinal numbering of pages system.
The server does not need to be tasked with an overload of requests to maintain your website’s peak performance.
Paginating the data feed is an excellent way of making sure the server requests run smoothly and effectively.
Doofinder’s Feed Pagination
To activate Doofinder’s feed pagination, you need to contact the support(link to contact form) team and make the request. However, before contacting us, ensure that your server has the following two parameters to retrieve a paginated feed:
limit: This is the maximum number of items returned in the response for each server call.
offset: This is the position of the first element that must be returned in response to the current request. The first value for this parameter is
0. This value increments in
limitwith each request.
Also note that depending on how the pagination is implemented, the feed can actually return
<limit> items or less.
For instance, if you implement it to get the items with
offset <= id < (offset + limit) you can get less than
<limit> items because some items with an id that matches the condition may be out of stock or simply were deleted.
If you instead implement it just to request your database with the very same values for
limit, your database will always return
<limit> items, until there’re no more results or the last set of results, is smaller than
<limit> in length.
Doofinder will start gathering pieces of the feed using the limit and offset parameters until it gets an empty response.
Upon setting the limit, Doofinder will make requests starting from
offset=2000 and so on until an empty response is received. Of course, along with the offset parameter goes the limit parameter which specifies the size of the page (1000 in this case).
Say we have a feed at http://server.com/doofinder.cfm, which has 6300 products in its data feed. We then set its pagination limit to 2000 items.
The first server request to our parser would then be:
This would fetch the first 2000 items under the following conditions:
- When the feed is an XML, this would also fetch the declarations at the beginning of the XML file.
- When the feed is TXT, this would also fetch the file’s header.
Consequently, the next request would be:
This would fetch the items between 2000 – 3999.
⚠️ Warning: Special care should be taken when the feed is an XML or CSV feed such that the beginning of the XML is not resent with the data.
This would be under another request with offset 4000: http://server.com/doofinder.cfm?limit=2000&offset=4000
A request with the offset set at 6000 would fetch the last 300 items. When the feed is in XML, this would also fetch the XML closing tags.
The final request would then get an empty response, signalling Doofinder’s downloader to end the download process.