
Originally Posted by
Wolffy
Or create the dropdown with the lesser of (a) the number of seats available or (b) the maximum number of seat sa user can buy at once. It would be necessary to then check again that the number of seats requested are still available when the user submits the request in case those available seats went to another user. You would probably do this anyway when you accept payment from the user (assuming the application does this).
Then there is the Ticketmaster model, which actually reserves the seats for a period of time (like 3 minutes) until payment is confirmed -- otherwise, the seats are returned to the pool. However, this is more complicated application.
hmmmmm the first suggestion sounds good to me.
I have 3 price ranges so im guessing i would need the user to select if they want to sit, (front, middle or back row) then select how many tickets they want.
I asume i would validate what is "available" with a price range the user selected. If all is ok, then insert the records?
Centurion, February 10th, 2010 06:01 AM
Bookmarks