- Sep 20, 2005
- 9,955
- 2,498
- Thread starter
- #21
But that's a completely different issue to the speed at which credit cards can be processed. If the problem is the time that people spent logged in it doesn't matter if they could process a million transactions a minute if they can only have 10 people logged in at a time and each of the 10 stays logged in for half an hour.
So the issue is how many people can be logged in at the same time. Obviously a tricky one, because you can't have a free for all, but rather than yammering on about the number of transactions they can make in a minute they should look at a way of easing the congestion caused by this bottleneck.
OK I'll give it another go :grin:.
The system has a gateway server. That means that people queue to log on and buy their tickets. The reason for this is so that once they are logged in, the booking system doesn't crash. As a member who used seatbooker last season and ticketmaster before they introduced the gateway server, I can tell you it has improved this aspect.
So the number of people that can be logged in and booking tickets is limited so the system won't crash. Now if those people (say 250) take 15 to 20 minutes to book their tickets, that means that those waiting will have to wait longer than if those in the booking system only took 5 minutes with their booking.
I don't know how to explain it any more plainly than that. Perhaps it would be easier if you joined the Trust and went along to the next meeting!