pote

+1

The last ID [is stored as a separate Redis key](https://github.com/soveran/ohm/blob/master/lib/ohm/lua/save.lua#L40) at `:id`. You could get the last ID with a Redis GET: ```ruby Ohm.redis.call("GET", "User:id") ```

@katecanaveral regardless of the last id feature, I'd want to comment on a possible source of bugs with your approach. If timed just right, you might get an incorrect `name`...

Maybe just having more explicit exceptions that suggest the standard solution to the problem would be enough? @katecanaveral this happens because you'd have to set to nil the attribute in...

Yeah, Disc is absolutely not thought out to be used as a message queue across different applications. Let's leave this here to encourage discussion, but my first thought would be...

Yeap, I've been thinking about this for a while. As I want to keep Disc as simple as possible, as a starting point I was thinking of including things like...

I think dropping Celluloid and having a single code path are good things, however I'd like to move to something that won't break the non-threaded mode at least, what are...

@cyx still doing a bit now and then. :)

I think specialization is key: PUBSUB is already available in Redis, and Disque is built to solve an entirely different use case.

Excellent question! I'm afraid that the answer will be disappointing though: Philote simply doesn't have clustering capabilities at this point in time, a single node is assumed. It's long been...