Fixing incorrect max check

Because currentOffset is updated with the itemsReturned prior to
checking if the max was hit, adding itemsReturned again to
currentOffset will cause an incorrect max hit
Merge pull request #3 from ajwalters/fix-incorrect-max-check

Fixing incorrect max check
Merge pull request #4 from lingo/master

Bugfix: Not checking for JSON.stringify and falling into endless loop.
Merge pull request #5 from lingo/master

Fixup mistake in merge
added function that enables users to react to network errors and server errors. Also added a function that allows users to tell the autoscroll to stop
Merge pull request #9 from droope/master

Added two optional parameters: onError and stopFunction
Upgrade jStorage to latest upstream