4 ms·
Interesting. It feels like it bleeds a bit too much of the underlying "Akka-ness" out into the actual everyday implementation of the library, which makes it fee
by weego 13y ago
Interesting. It feels like it bleeds a bit too much of the underlying "Akka-ness" out into the actual everyday implementation of the library, which makes it feel slightly more boilerplatey than perhaps is needed.
I noted that Debasish Ghosh recently updated his redis client to have Akka as the underlying handler as well.
- yummyfajitas 13y agoBleeding out the akka-ness is a feature, at least if you live in akkaland. For example: path("get_a_list" / PathElement) { externalKey => get { complete { for { internalKey <- redis.get("internal_keys_from_external":externalKey) finalResult <- redis.smembers(internalKey) } yield (finalResult.toList) } } } Spray already expects an akka future, as does everything else, so this library fits in perfectly.
- shpxnvz 13y agoAnd it appears to use futures that are part of Scala core (which Akka now uses as well) so I'm not sure how much this can be said to be Akka-ness anyway.
- etaty 13y agoYou are welcome to create a issue or a pull request. Rediscala needs an akka actor System and sometime replies are of type ByteString.