This adds pagination as a keyword argument to create_api. However, we already allow offset and limit in our search queries. Should we allow both?
For example, if I specify limit 10, offset 3, and page size 4, the result will be a response that comes in three pages, of sizes 4, 4, and 2 in that order, with results from 3 through 6 in the first page, 7 through 10 in the second page, and 11 through 12 in the third page.
Fixes issue #59.
Merge branch 'master' into pagination
I think for now we can allow users to use either pagination or limit/order (or both, though one can be mostly simulated with the other). We should note in the documentation that for simple applications, using pagination should be fine, but for more advanced applications, limit/order can be used.
Fixed sphinx bug and added note about using limit and offset with pag…