Hi,
I am posting this question on behalf of our web department:
It is our understanding that the Tessitura web API has a caching process to improve response time and reduce database traffic. Sometimes in testing, we make configuration changes that will cause different results, but we often have to wait for the API cache to expire before we can see our changes in our test results. This causes uncertainty in our results. Is there a method we can call to cause Tessitura API to flush its cache for all sessions? Based upon our question, is there something in this area we misunderstand or could handle better?
Thanks in advance,
Jeri
I just bounce the application pool in IIS and that seems to do the trick.
I have a related question. We have been having issues with performances becoming available online at the exact time we have specified because the GetProduction and GetPerformance calls are cached for 10 minutes after the initial call...this means that if someone hits the site 1 minute before a performance is set to go on sale the on sale indicator returned is still No and will remain so until the 10 minutes pass.
So the question for us is, is there a way to clear the cache for said calls without bouncing the entire application pool?
Taking that a step further, how are other orgs dealing with getting shows to appear when they are supposed to?
With version 10 there is an API method named DestroyCache that clears the cache without disabling API access - I haven't implemented it yet so I can't provide any information as to the database strain this would cause, but you could call DestroyCache at the initial page load of a user's session.
Or, if that would be overkill and you do have a major concern about people missing the on sale time, you could create a program that would run at exactly the on-sale time and call DestroyCache.
Good luck,