#social 2015-08-05

2015-08-05 UTC
jasnell, bblfish, jaywink, tilgovi, the_frey, the_frey_, jaensen, almereyda, jasnell_, Lynn, csarven, melvster and kk joined the channel
#
aaronpk
paging by page number is dangerous
#
ben_thatmustbeme
yeah, especially for high volume, where by the time you read page two, there might be a new item inserted, and now you are getting double entries
#
aaronpk
much better to handle paging by offset referring to specific objects
#
ben_thatmustbeme
the reddit method as i call it. as thats the frist place i really saw it used :P
#
ben_thatmustbeme
totalItems may change as well while paging through
#
aaronpk
paging by page number means the contents of URLs is changing constantly. paging by reference means pages will always have the same things on them
#
ben_thatmustbeme
aaronpk: (assuming no deletes)
#
ben_thatmustbeme
unless you mean paging by X to Y
#
aaronpk
since that gets indexed by search engines, I don't have to worry about people finding a page in a search result and then not seeing the content they were expecting
#
ben_thatmustbeme
maybe take this to that github issue
#
ben_thatmustbeme
that is the nice thing of just saying "pageOf" you don't depend on page numbers
jasnell and jaywink joined the channel
#
jasnell
aaronpk: the page numbers in the example are just part of the example
#
jasnell
the paging model does not depend on page numbers at all
#
jasnell
that just happens to be how I wrote up the quick examples. The proposal deals more with the separation between the Collection and a CollectionPage
#
csarven
owl:unionOf ( as:CollectionPage as:Link ) is pretty clear to me.
KevinMarks joined the channel
#
KevinMarks
the opensocial paging used item number which wasn't ideal. It also had timestamp binding
the_frey, KevinMarks, Mattg_ and pfefferle joined the channel