Internal caching schedule for RON1 and RON2

The caching on RON1 varies depending on the server load, however the following is the standard cache schedule in minutes:

define ( "TTL_HOSTS" , 5 ); ## The host list from the directory.

define ( "TTL_HOSTDETAILS" , 5 ); ## Additional details for a specific host.

define ( "TTL_TOURS" , 5 ); ## Tour codes and names.

define ( "TTL_BASES" , 0 ); ## Bases for a specific tour.

define ( "TTL_TIMES" , 10080 ); ## Times for a specific tour.

define ( "TTL_PICKUPS" , 2880 ); ## Pickups for a specific time and basis.

define ( "TTL_ROUTES" , 1440 ); ## Operational routes for a specific date.

define ( "TTL_PRICES" , 15 ); ## Price array for a specific trip.

define ( "TTL_AVAILABILITY", 5 ); ## Availability array for a specific time and date.

define ( "TTL_WEBDETAILS", 43200 ); ## Web details for a specific tour.

Cache load frequency for RON2 and TTL in minutes:

Every 15 min: next 7 days for all tours times and basis (expire_time=900)

Every Hour: from day 8 to next 30 days (expire_time=3600)

Every 12 Hours: from day 31 to next 90 days (expire_time=43200)

Every Day: from day 91 to next 364 days (expire_time=86400)

This is correct as published at 14:37 15th August 2018 for documentation purpposes but may change at any time without notice.

For urgent enquiries, contact tickets@respax.com regarding RON Cache TTL's