4 ms·
back then, when a user selected seats, they were temporarily "locked" (at least from our end). If other users were "browsing" seats, they would see those seats
by jason_slack 10y ago
back then, when a user selected seats, they were temporarily "locked" (at least from our end). If other users were "browsing" seats, they would see those seats as unavailable. Honestly, we did this because it was easier to "lock" the seats as it made searching easier for other users on the systems. It lessened the e-mails that said: "I thought I had these seats XYZ picked, but I didn't get them...". We weren't really being nice, but it came off that way.
If a user took longer than the 4 minutes or so there would have had to be more users on the system wanting the same type of seats and none available. This really didn't every happen except for insanely popular events, like NYE or some very popular singer, etc. If after 4 minutes, your time was up. You were taken back to search again, but we said "your last seats are still available. Check out now?".
I cannot say now-a-days, if the timer has more importance and I cannot say from a Ticketmaster standpoint technically. What I can say is how we used to do it.
Edit: added the "Honestly" part, first paragraph.
- ritchiea 10y agoThe timer is/was the worst, I once decided not to buy tickets for an event because the timer wasn't giving me enough time to fill out my CC info and I didn't want to bother rushing or filling out some kind of user profile w/saved card to fit their awful UX.
- patmcguire 10y agoTimer is not sketchy if it's long enough, but four minutes is probably too short. You need locking for the reasons you said, and if you didn't have an expiration you'd have fun denial of service either accidentally from users deciding not to purchase, or purposely for the sheer malicious joy or from resellers who would scalp a ticket for a higher price, then use their lock to buy the actual product. Fifteen minutes seems more appropriate, though.