Question

I’m trying to write a web application in ASP.NET MVC that allows each user to vote for multiple pictures but does not allow them to vote multiple times for the same picture. Users are not authenticated. What should I save in the database or in cookies?

Answer 1

With anonymous users, you have two options, neither of which are very good:

1) Track the user with a user id stored in a cookie. As long as the cookie persists. the user can’t vote twice. However, they can delete or otherwise modify the cookie. They might have cookies turned off. They could have two different browsers open at the same time. Scripts for “cheating” (curl http://site/vote?score=5&pic_id=1) won’t store a cookie anyways. Basically, you’ll end up with people voting more than they should.

1.5 *

2) Track the user by IP address. This is essentially the opposite. Users can’t vote twice, regardless of deleting cookies, switching browsers, etc. However, several people from the same household (using a DSL router) can only vote once combined. Many companies will similarly hide many users behind a single IP address. I think some ISPs do, too (AOL?). You’ll end up with far fewer “votes” than legitimately should have been recorded.

So the question is do you want over or under votes? If you think cheating is likely, I’d go for #2. But if cheating is likely, that means there’s an incentive. And if people realize their votes aren’t counted (which they may not realize), they’ll be unhappy.

After that, whether you store each vote as a row, or combine the votes into a single row (update pictures set num_votes = num_votes + 1, total_score = total_score + [submitted score]) is up to you.

• 1.5 The third option would be to record their vote and an email address, send them the email with a confirmation link and ask them to click it to record their vote. People can still cheat with fake email addresses, but it’s not as likely as deleting a cookie.