3 ms·
Many ticket-limited events have figured out how to run a massive timed purchasing event like this. TicketFly could have checked out any one of them to learn how
by peterwwillis 12y ago
Many ticket-limited events have figured out how to run a massive timed purchasing event like this. TicketFly could have checked out any one of them to learn how to properly execute this kind of event, and prevent "line-skipping". (ShmooCon and Playa Del Fuego are two such events i'm familiar with)
The system is very simple: you open up the ticket purchase page a few minutes before registration opens. The page reloads at randomish 30-second intervals. Once registration opens, the backend sets a queue number linked to a unique ID, and sets a cookie in your browser with that ID. You wait for the page to finally reload and say "it's your turn to purchase tickets!" And so, through a delayed system of individual registrations, everyone gets their ticket if they showed up at the appropriate time.
The 'queue' is a server-side aspect of this system, and it all happens on servers that have their clocks synchronized. Before accepting anyone into the queue, the server software needs to check if it's 12:00 yet (or whatever time registration opens).
Their software did not check the time before populating the queue. Bottom line: this was a bug in TicketFly's software, not "hacking".
- djcapelis 12y agoUhm. Shmoocon and Playa Del Fuego sell... what, 2,000 tickets? Burning Man is selling 70,000 this year. 40,000 were sold in this single sale alone. That's an order of magnitude difference.
- peterwwillis 12y agoThe design is scalable to any ticket amount, given enough time and servers. You accept connections and assign queue numbers and then delay purchasing. You add randomization of various requests and entry in the queue itself to prevent gaming or latency-derived unfairness. I've worked on websites that return hundreds of thousands of dynamic content pages per second, and you don't even need to do that here: all you need is a landing page that sets cookies, and then you can take all day to actually allow people to purchase with the reservation number they've got. The bug has nothing to do with any of that, though...
- forgottenpass 12y agoThat's entirely irrelevant unless you're arguing that 40k (and/or N number of attempted buyers) are too many items to manage in a queue on the server side. Is that what you're saying?
- beambot 12y agoGo look at the Comic-Con registration then. Theirs is something like 130,000?