06:55:40 GMT <mattberther> Most of what Ive read seems to indicate the pattern for a FIFO queue is to build a redis list, and have the values in the list be keys to other objects in the store. is there a recommended pattern for implementing a FIFO queue -- where data in the message can change?
16:09:23 GMT <NehezvoltRegelni> Hi folks! How am i supposed to have one transaction, that increments a key, sets another key's value to that new variable in redis js?
16:12:37 GMT <minus> NehezvoltRegelni: either WATCH/MULTI/EXEC (can fail and you have to retry) or a Lua script (always atomic)
16:13:26 GMT <NehezvoltRegelni> my problem is (other than that i'm a newb in nodejs) is that i can incr a key's value, but get is async, so how do i gonna get to that into another key's value form the same event
16:15:05 GMT <NehezvoltRegelni> http://redis.js.org/#api-clientmulticommands it even says in the code's comment that that callback is not atomic
16:15:14 GMT <minus> if you need atomicity a lua script is your only choice
16:15:45 GMT <minus> but often you don't really need that if you just order your operations correctly and maybe make use of rpushlpop
16:21:12 GMT <NehezvoltRegelni> minus: but i'm in nodejs, an event driven thingofabob
16:21:31 GMT <NehezvoltRegelni> i can use multi, but i can't get a previous operations value as that would be async and out of transaction and world, even
16:21:48 GMT <NehezvoltRegelni> i don't see how lua can come into redis.js jet, but i'm rtfming
16:25:28 GMT <minus> NehezvoltRegelni: see EVAL, it runs a lua snippet inside redis
16:34:30 GMT <NehezvoltRegelni> minus: thx!