Jeremy Custenborder

@uzunbaz What are you thinking? Just a configuration setting with the number of milliseconds until an expiration and then applying that to all `SET` calls?

Ignoring the fact that we need to use `SET` instead of `MSET` how would we want to calculate the the value for `EX`? As a static config setting? So something...

@lmeadors Hmmm I haven't thought about that. The goal was for v2 to be backwards compatible with v1.

Well my goal was to keep the original class name and make it backwards compatible. I was going to log a warning telling you to move.

@isaranchuk I don't have anything planned at the moment. We could definitely add this. In this case the key is lat, long? This would take a refactor of the connector...

@isaranchuk I took a few minutes and read through the [Geospatial best practices](https://redislabs.com/redis-best-practices/indexing-patterns/geospatial/). Looking at the following example of the protocol we need 4 pieces of data: ``` GEOADD cars...

``` GEOADD cars:bmw -115.17087 36.12306 my-car ``` For sets we could do something like this. We could drive the set key based on the topic. **topic: cars:bmw** You can use...

@StRobiEst Did you find a solution for this?

Ahh boo. Thanks for following up! Much appreciated! On Sat, Oct 10, 2020 at 12:19 PM StRobiEst wrote: > Sadly i did not find a reliable solution. > > —...

Hey Matt! Thanks for the pull request. Have you looked at examples/fullstack? This has a docker-compose script of the whole platform. On Mon, Jun 13, 2016, 5:15 PM Matt Maybeno...