Via Tender: Search paging session
Reported by Travis Bell | January 6th, 2012 @ 03:45 PM | in Icebox
Assigned to Tender discussion #144. As reported in Tender:
The second issue is a potential concern, not an issue I've actually come encountered so far. Typically when getting pages of results, you have an ID or time stamp, something to track to ensure subsequent pages match pages you've already pulled. Otherwise, content updates server-side could cause results to be sorted differently between pages, new results to appear, and old results to disappear, and just bad things in general on the client side. From what I understand, the API servers are independent from the website, and changes on one are delayed from showing up on the other. Depending on how precisely scheduled the refreshes are, this could could be something as simple as marking search results stale if requests happen on different sides of say Midnight GMT.
Comments and changes to this ticket
-
Travis Bell July 23rd, 2012 @ 12:20 PM
- Milestone changed from “Icebox” to “Jerry Maguire”
- Milestone order changed from “31” to “0”
-
Travis Bell July 23rd, 2012 @ 01:57 PM
- State changed from “new” to “invalid”
- Tag changed from “feature” to “feature”
- Milestone changed from “Jerry Maguire” to “Icebox”
- Milestone order changed from “27” to “0”
I don't think the search session var is particularly useful unless we can move away from not having to cache our search results. For now, I'm closing this ticket.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Travis Bell