KPI to be measured
Ask a question
Was this article helpful? 1 out of 1 found this helpful
Some web services are typically designed to help integrators in developing front-end projects, in which it is necessary to have very small response times in order to ensure an appropriate user experience. For this reason, the response of these services is cached.
Typically this happens for any web service using the GET method. In THRON there are some alternatives that leverage POST method, and which can be used to realize backend integrations, without incurring in cached responses. Please be aware that the response bodies of the different methods do not return the same information: more specifically, the GET methods for front-end projects typically contain information related to delivery integrations (e.g. the channel urls, the embed templates...) whereas the POST method typically returns all the set of information required for backend integrations (e.g. contentIds, caategoryIds, prettyIds, tags...).
These are the GET methods for front-end projects integrations and their alternatives:
|
Front-end: GET web service |
Backend: POST alternative |
Purpose |
| getCategory | findByProperties2 | To retrieve all the information on a specific folder (or set of folders) |
| getContentDetail | findByProperties | To retrieve all the information on a specific content |
| showContents | findByProperties | To retrieve all the information on a specific set of content |
Below are listed some of the main delivery web service (or class of web services) and their corresponding cache duration:
| Service | Cache duration |
| //<clientId>-cdn.thron.com/delivery/public | 60 seconds |
| //<clientId>-view.thron.com/api/xcontents/resources/contentlist/showContents | 60 seconds |
| //<clientId>-view.thron.com/api/xcontents/resources/delivery/getContentDetail | 60 seconds |
| //<clientId>-view.thron.com/api/xcontents/resources/delivery/getThumbnail | 1 hour |