Mark Grey
Mark Grey
As a user of AWScala's dynamodb module, I have found some success defining a [typeclass converter](http://danielwestheide.com/blog/2013/02/06/the-neophytes-guide-to-scala-part-12-type-classes.html) for my types to provide encapsulated serialization into AttributeValues. I might be good to...
The present implementation [coerces sequences it can't determine the type of to a string set](https://github.com/seratch/AWScala/blob/master/src/main/scala/awscala/dynamodbv2/AttributeValue.scala#L31) and calls `toString` on it's members. This simple form of improvised serialization can work in...
https://github.com/seratch/AWScala/blob/master/src/main/scala/awscala/dynamodbv2/AttributeValue.scala#L14 I've been thinking about perhaps reimplementing this to provide a more fluent interface. Since the types that come back out of the nested maps are the vanilla-java AttributeValues, traversing...
It would be nice to be able to manipulate the values returned from dynamo on get and put operations using the [ReturnValues](http://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_PutItem.html#API_PutItem_RequestSyntax) construct.
Was wondering if you'd be interested in contrib for support on a newer version of the AWS java sdk? It would be cool to have access to the newer Dynamo...
Right now, pulls are saved on a per-cookie basis. We should also scale clicks/reward by unique users for a more accurate underlying reflection. This could be accomplished by making storage...
Right now, preventing repeated rewards is left up to the user implementation. This should be improved by codifying the practice into a reward_and_redirect decorator.
In order to make steps towards #8, a persistency solution that takes snapshots of changing bandit state is needed. This could be built off of python's core [rotating log file...
Although it's not widely used, ZODB seems like a pretty good drop-in storage solution for POPO's like the bandits, and since it's persists to a file it's a pretty lightweight...