Merge branch 'master' into unstable
add support for index scan direction to query and queryOnce methods

the index scan direction was previously only available for queries on secondary indices (an oversight)
bump AWS SDK version to 1.5.8

AWS SDK 1.5.7 did some refactoring to progress events, which has resulted in some unavoidable deprecation warnings, and there is no choice but to wait on improvement to the SDK
bump AWS SDK version to 1.6.0

resolve SDK’s refactoring to progress listeners
allow queries with limits and scan direction
renames; remove seq.view; expose totalLimit in hash key query api method; add total Limit as param to hash and range key query instead of a different api method
add totalLimit to the scala doc for the api methods that expose it
expose totalLimit in the query by secondary index method as well
d'oh. forgot to pass on the totalLimit arg
Merge pull request #9 from pellucidanalytics/allow-limit-query

allow queries with limits and scan direction
first draft at fixing overloading on query

needs work…
tidy docs for query overloads
fix query logic to only give 'totalLimit' results when batch size > totalLimit
minor: reformulate 1020743

attempt to simplify conditional logic
pull apart the result set mutation and the decision about whether to recurse
simplify the decision to recurse
Merge branch 'fix/query-logic' of github.com:pellucidanalytics/aws-wrap into fix/query-logic

Conflicts:
	src/main/scala/dynamodb/mapper.scala
Merge pull request #10 from pellucidanalytics/fix/query-logic

Fixes: total limit query logic and overloading compile issue (Corrects #9)
Merge branch 'unstable' as v0.5-RC3

Pull in latest changes from unstable branch:
- add support for index scan direction to query and queryOnce methods
- update to AWS SDK 1.6.0 (small internal changes to S3 wrapper)
- add support for limiting the size of the result set for query
- improve the overloading of query