It gets fuzzy once you introduce replication into the picture. Temporary
keys should always be random, anyway, as a matter of hygiene.

IMO, the code should avoid methods that store keys. Is this operation
possible without the store component?
On Feb 3, 2014 9:14 AM, "soedar" <notifications@github.com> wrote:

> In views/game/board.js:
>
> > +                res.json(output);
> > +                done();
> > +            });
> > +        }
> > +
> > +        var key = 'leaderboards:' + game + ':' + board;
> > +
> > +        if (friendsOnly) {
> > +            user.getUserIDFromEmail(client, email, function(err, id) {
> > +                if (err) {
> > +                    res.json(500, {error: err || 'db_error'});
> > +                    done();
> > +                    return;
> > +                }
> > +
> > +                var interstoreKey = key + ':' + id;
>
> I was under the impression that the redis transaction calls would be
> serialized and atomic. Is the random component still necessary if we
> create, retrieve and delete the interstoreKey in one atomic step?
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/cvan/galaxy-api/pull/52/files#r9390485>
> .
>