it's for a caching strategy, so the document will still be available and if fetched again will again move upwards in the list as to be retained

if people make use of it to read and search the bible it will not ever fall above the high water mark and its access counter will continue to escalate, ensuring it is unlikely to fall below even with a lull in usage

Reply to this note

Please Login to reply.

Discussion

The complex thing is that each verse will be a separate event. Since our events are nested, they may access part of an index, but not each individual section.