12306 new version of brush ticket software design Thinking

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/5B/56/wKiom1UGZv3iZ5DbAAJJnFUfswk663.jpg "title=" 6eef2b32-360b-484c-8674-cb5d379463ff.png "alt=" Wkiom1ugzv3iz5dbaajjnfufswk663.jpg "/>

12306 Web site in today's new verification code enabled, from a simple number changed to the Chinese name of the item, select the corresponding photo.

On Weibo, after knowing the news, went to 12306 stroll around, and then began to think about this verification code can be on the Ox scalper and brush ticket software how much role.

At the beginning of the thinking that the verification code is more difficult to brush the ticket, the ticket is only used to replace the manual operation of the software. First identify the Chinese, and then find the corresponding picture, unless there is a whole 12306 of all Chinese and picture corresponding relational database, or is to identify the Chinese can not find pictures, pictures are photos, with software can compare the picture is the same, but it is not possible to use the identification software to see the photo content, if you can recognize it, Scalper directly develop photo recognition software to make money than swipe tickets.

So the key to this problem is the Chinese and image relational database.

Later in the discussion with friends, found that this problem in today's internet Big Data era also has a solution.

method is similar to the WiFi password sharing principle, let the user to manually identify, identify the correct, then write down the Chinese, pictures and correspondence, after the human flesh more, all the problems and verification code is traversed. Because like this Chinese and the verification code is not randomly generated, it is always a fixed relational data.

There are, of course, some limitations to such schemes.

1, brush ticket software needs a certain base of the user group.

This is not a problem for a software company like 360 and Cheetah, but it will improve the threshold for scalpers to brush the ticket software. Ox's brush ticket software will not have a large number of user groups, so want to accumulate verification code data need to hire people to identify, and 12306 can at any time enter a new verification code data, the database to improve to 1.001 billion, and the artificial cost of cattle will be greatly improved.

2. Storage of data pictures

It can be inferred from the previous question that this code database is increasing in the end there is likely to be more than 1.001 billion, the data, especially the storage of images is a problem, Internet companies can store this data to remote server, OX software? Of course, the average PC is now completely able to store this data, but when a swipe software installation requires a G-space, and it needs to keep updating the data? This data to get updated so that the Ox brush ticket software completely divorced from the previous stand-alone mode of operation, OX software has become internet. Ox software can also be like internet companies, the verification code data stored on the remote server, but this will greatly increase the risk of scalping, the cost will increase.

3, data query, image comparison efficiency

People who know about the database should be able to know that the query for a single field is fast within millions if the optimization is reasonable. But after obtaining the key word of the verification code, we still need to do the comparison picture operation. After the verification code relational database accumulates, if a verification code keyword only corresponds to two pictures, then it is very easy to compare. But what if a keyword has 10 100 photos? How many times do I have to compare with 8 images to choose? How much impact this efficiency will have. Brush ticket Software response speed is an important link, before some brush ticket browser in the identification of verification code efficiency is poor, 12306 to enable the new verification code, brush ticket software If there is a picture comparison link, this efficiency will be how?

The above is the 12306 to enable the new authentication mechanism to think of, feel this revision on the Ox software impact will be relatively large, but the user base of the larger brush ticket browser is a new opportunity.

12306 new version of brush ticket software design Thinking