heh, yep, I meant that if there were multiple usefulness votes, the server-side code should replace them all for a single updated usefulness objects.
I was going to say that the only way I could think of that we could be generating multiple usefulness objects with the current code is if two requests come in at the same time to different app servers, but it doesn't seem that the client is currently doing this. Either way it definitely makes sense to look at other possibilities.
heh, yep, I meant that if there were multiple usefulness votes, the server-side code should replace them all for a single updated usefulness objects.
I was going to say that the only way I could think of that we could be generating multiple usefulness objects with the current code is if two requests come in at the same time to different app servers, but it doesn't seem that the client is currently doing this. Either way it definitely makes sense to look at other possibilities.