How to prevent swipe tickets based on WeChat OpenID voting system

An OpenID-based poll, which is now just a vote by acquiring OpenID and then judging UA.
Is there a better way to prevent the ticket from being brushed?

Reply content:

An OpenID-based poll, which is now just a vote by acquiring OpenID and then judging UA.
Is there a better way to prevent the ticket from being brushed?

openidIsn't it the only one?
Just remember.ip

1. For OpenID that has already been voted in, save the database.
2.openID This field should be indexed.
3.OK, each received a vote processing, first in the table to see if OpenID is recorded, there is no insert processing. Prompting the user for a ticket has been cast.

Upstairs has been answered very well, the database to save OpenID, and then every time there is no, OpenID added simply the purpose is to increase the speed of the query

You can use web page authorization to make sure that it is open in a browser. Without permission, you can use the door of sesame to borrow someone else's authorization. OpenID is unique

Very good, a user can not have 100 number at the same time, also not allowed.

Each time a user sends you a message there will be an OpenID, save the OpenID, so that you can vote to determine whether OpenID is his audience.

Subscription number words limit the user can only get votes through your public number url! For example, let the user reply to vote to get the URL, and then record the user's OpenID, the user vote after the OpenID, so that both the uniqueness of the OpenID, but also limited to prevent someone forge the OpenID brush ticket, while still can rise powder; certification service number can be used to authorize web pages

