Hello. Has anyone implemented e-ticket delivery using the print tickets method? I am interested in how people decided to make use of the byte array that can generate the barcode. And the mobile solutions. Has anyone decided to store the barcode with the user account or email it or generate it on the fly whenever a user requests it? Has anyone combined it with print at home ticketing in same email or separated it? If anyone can share some insight on any kind of solution or technologies the used in combination with this it would be much appreciated. Thank you.
Hello Andrei,
While I was at McCarter theatre I developed a mobile website that used this method to display the barcode for scanning on a mobile device. The website also had the option for the patron to send the ticket barcode via email to another person. The mobile website source code is on TASK as shared solution 325. In there you should be able to see a good example in code. If you want to see in it action I presented on this at the 2012 conference and my presentation has video in it.
Presentation link
http://www.tessituranetwork.com/tlcc/2012/Presentations/01-U_Web_Developer_Forum.pptx
Please let me know if you have any questions.
Regards,
Jon
Thank you very much for your answers and solutions. I will review them and get back to you if I have more questions. Thank you.
Hi,
I looked through the McCarter mobile website slides presentation/documentation and I have a few questions. Others feel free to advice even if you have a different implementation than the McCarter mobile website.
- How are the barcode tickets sent to the customers? I notice that there is a my shows section where they can view their tickets but I am also interested in how they get delivered to people. Especially when someone buys tickets for a group of people and then later on sends everyone their individual tickets. Do they receive an email with a link to the ticket and they open the link in a browser? Or are they emailed as attachment images or PDFs? I noticed that the ticket images are stored in a folder as {TicketNo}.png. If it is sent to people as a url that they can open in the browser I am assuming that the url is encrypted, otherwise the system could be abused as they would have the path and could keep trying ticket numbers as the ticket filename is the same as the ticket number. So if it is implemented as encrypted url, if you could help me learn more about how to do do that, it would be much appreciated.
- In the scenario where a user purchased multiple tickets to a show, I noticed that from the my shows section a user can select each individual ticket and send it to the designated recipient of the ticket. How does the application manage the association between the transaction, the tickets and the different recipients? When purchased is the user asked to specify the recipient of each ticket and each ticket is sent to the appropriate user? Or is the purchaser the only recipient of the tickets and then it's on the purchaser to forward the tickets/links to tickets to each recipient? Or send their individual tickets from the my shows section?
- Since the ticket images are stored in a folder, how is the storing of the tickets managed throughout the years. How risky is it to reach a gigantic folder structure and application size? Are the transactions and tickets recycled throughout the years? how often? or are they kept permanently?
-To start with a basic implementation, to just test out the print tickets method, I could use some guiding on how to take the result of the method and convert it to an image and save it in a folder.
Thank you all.