Webapi PrintTickets method

Hi,

I Thought I would ask some other questions on this topic. 

If you are using the PrintTickets method are you saving the files on your server or do you have handler that takes one ticket at a time and return the data in the reponse for each ticket?  Or maybe do you use a data uri  and embed the image data in the source of the image tag. 

Any thoughts?

Thanks!
Jon

We started using this about two months ago. Instead of using the Tessitura Print at Home app, we are using the PrintTickets method to render tickets in a browser window, so patrons can print them, both after purchase and from purchase history in their profile.

We are saving the images to the server. For security purposes, we have a job that purges the ticket images regularly.

The one major issue we found with the method, the documentation and the supplied sample from the network  is that it does not return the image rotation as designated in the ticket design template.  So, a vertical-rotated barcode in ticket design always comes through as horizontal from the API.

Thanks,
Patrick

We started using this about two months ago. Instead of using the Tessitura Print at Home app, we are using the PrintTickets method to render tickets in a browser window, so patrons can print them, both after purchase and from purchase history in their profile.

We are saving the images to the server. For security purposes, we have a job that purges the ticket images regularly.

The one major issue we found with the method, the documentation and the supplied sample from the network  is that it does not return the image rotation as designated in the ticket design template.  So, a vertical-rotated barcode in ticket design always comes through as horizontal from the API.

Thanks,
Patrick

Thanks Patrick.  What are the rules for purging data?  Do you have somethign in the name of the file to know when to delete it?  Also are you seeing large amounts of images being stored ?

Thanks,

Jon

We purge it every 24 hours. We intend to purge it hourly if it gets to be an issue.

We have a parent directory where all the contents are wiped every 24 hours. We use order number & ticket number in the filepath of the subdirectories as well, on the off chance that someone were to try to script against it, it would be extremely difficult to find the images. 

The images are only like 10k each, so they aren't too large. We're still in our pilot period and have only rolled this out at 2 venues so we haven't had excessive data stored yet. Once we roll this out at all 7 venues, it might be more of an issue.