I agree it shouldn't be the responsibility of the client to prevent the user from submitting multiple usefulness votes for the same review (though if it wants to do so as for some usability enhancement, neat).
On the server side, that bit of code could be rewritten to replace any current usefulness vote(s?) for that user-and-review if there is any.
I agree it shouldn't be the responsibility of the client to prevent the user from submitting multiple usefulness votes for the same review (though if it wants to do so as for some usability enhancement, neat).
On the server side, that bit of code could be rewritten to replace any current usefulness vote(s?) for that user-and-review if there is any.