V
V
Hi, Go ahead Probably something new in 3.0 On Mon, Feb 29, 2016, 19:33 Shikhar Bhushan [email protected] wrote: > http://redis.io/commands/spop > > vs > > def spop[R: ByteStringDeserializer](key: String): Future[Option[R]]...
What you want, has already been done, you just have to send the right message. https://github.com/etaty/rediscala/blob/master/src/main/scala/redis/actors/RedisSubscriberActor.scala#L60-L74 I don't advise against overriding the receive, but it is a poor choice when...
Any redis clients will try to reconnect to the server every 2s if the connection is lost.
No the client is always connected to the server. If you use a pool you can dispatch the connexion on many redis server, (or put the same server multiple times...
Yes it will round robin the connections. if your CPU is not already overloaded with just one you can add more for more throughput
Yes, because you can't write a ByteStringDeserializer[Long] for any ByteString.
Hum I see, you are right. DoubleRedis should/could be hidden? (It should be hidden as it is Redis specific) https://github.com/etaty/rediscala/blob/master/src/main/scala/redis/Converter.scala#L183-L193