sakaiproject/Hilary — pull request #299 by mrvisser (2012-12-15 22:20:56+00:00)
Title: Make paging parameter optional for general searches

Currently a `start=0` has to be passed in order to get the first page for a general search.
The problem with this is that the UI doesn't have enough context to determine which type of paging data to send along.

For example the paging on my library looks like `/api/user/content?start=lastModified:contentId`.
While the paging for general searches looks like `/api/search/general?start=0`.

The infinite scrolling plugin gets the paging key off of the last item in the initial list it has rendered.

Having an optional first page paging parameter would solve the issue.