> There could be instances where a number of items is removed from an infinite scroll list (lets say the last item included). Removing the items could bring the results higher up and trigger the load of the next set of results, however at that point the nextToken would have to be based on a different item and would no longer be valid. This might also be a fairly significant change to the infinite scrolling plugin.

I'm pretty sure in this case you can still just use the `nextToken` to get the next page of items. It won't care the intermediate items were deleted. I'm not happy putting the sort key into the discussion model because it will be different in different contexts. I'd like to try and avoid it.

> Also, I'm not sure how this works as the Ajax call would only be able to receive a single response/object ?

The library results is an envelope with a `results` array. So now it looks like:

```
{
  'results': [ ... ]
  'nextToken': <nextToken>
}
```