Return to Answer

###Request Caching In the interest of application performance and to prevent inadvertent api 'abuse', Soapi.js includes an integrated request cache that stores the results of each unique request url for a default (and minimum) period of 60 seconds.

The caching duration may be increased for individual routes as per your application's needs.

e.g. perhaps your application requires that the stackauth site list be current to only 10 minutes you may set an increased cache duration as follows:

Soapi.RequestCache .setDuration(Soapi.Routes.SitesRouteMap.routeFormat, 60000 * 10); 

After a successful response, subsequent requests to /sites within the cache duration will be returned from the in-memory cache. Upon expiration of the cache duration, the data for the particular route is purged from memory and the next request will be forwarded to the API.

Next: Throttled Request Queue

Request Caching

In the interest of application performance and to prevent inadvertent api 'abuse', Soapi.js includes an integrated request cache that stores the results of each unique request url for a default (and minimum) period of 60 seconds.

The caching duration may be increased for individual routes as per your application's needs.

e.g. perhaps your application requires that the stackauth site list be current to only 10 minutes you may set an increased cache duration as follows:

Soapi.RequestCache .setDuration(Soapi.Routes.SitesRouteMap.routeFormat, 60000 * 10); 

After a successful response, subsequent requests to /sites within the cache duration will be returned from the in-memory cache. Upon expiration of the cache duration, the data for the particular route is purged from memory and the next request will be forwarded to the API.

Next: Throttled Request Queue

###Request Caching In the interest of application performance and to prevent inadvertent api 'abuse', Soapi.js includes an integrated request cache that stores the results of each unique request url for a default (and minimum) period of 60 seconds.

The caching duration may be increased for individual routes as per your application's needs.

e.g. perhaps your application requires that the stackauth site list be current to only 10 minutes you may set an increased cache duration as follows:

Soapi.RequestCache .setDuration(Soapi.Routes.SitesRouteMap.routeFormat, 60000 * 10); 

After a successful response, subsequent requests to /sites within the cache duration will be returned from the in-memory cache. Upon expiration of the cache duration, the data for the particular route is purged from memory and the next request will be forwarded to the API.

Next: Throttled Request Queue

###Request Caching In the interest of application performance and to prevent inadvertent api 'abuse', Soapi.js includes an integrated request cache that stores the results of each unique request url for a default (and minimum) period of 60 seconds.

The caching duration may be increased for individual routes as per your application's needs.

e.g. perhaps your application requires that the stackauth site list be current to only 10 minutes you may set an increased cache duration as follows:

Soapi.RequestCache .setDuration(Soapi.Routes.SitesRouteMap.routeFormat, 60000 * 10); 

After a successful response, subsequent requests to /sites within the cache duration will be returned from the in-memory cache. Upon expiration of the cache duration, the data for the particular route is purged from memory and the next request will be forwarded to the API.

Next: Throttled Request Queue

###Request Caching In the interest of application performance and to prevent inadvertent api 'abuse', Soapi.js includes an integrated request cache that stores the results of each unique request url for a default (and minimum) period of 60 seconds.

The caching duration may be increased for individual routes as per your application's needs.

e.g. perhaps your application requires that the stackauth site list be current to only 10 minutes you may set an increased cache duration as follows:

Soapi.RequestCache .setDuration(Soapi.Routes.SitesRouteMap.routeFormat, 60000 * 10); 

After a successful response, subsequent requests to /sites within the cache duration will be returned from the in-memory cache. Upon expiration of the cache duration, the data for the particular route is purged from memory and the next request will be forwarded to the API.

###Request Caching In the interest of application performance and to prevent inadvertent api 'abuse', Soapi.js includes an integrated request cache that stores the results of each unique request url for a default (and minimum) period of 60 seconds.

The caching duration may be increased for individual routes as per your application's needs.

e.g. perhaps your application requires that the stackauth site list be current to only 10 minutes you may set an increased cache duration as follows:

Soapi.RequestCache .setDuration(Soapi.Routes.SitesRouteMap.routeFormat, 60000 * 10); 

After a successful response, subsequent requests to /sites within the cache duration will be returned from the in-memory cache. Upon expiration of the cache duration, the data for the particular route is purged from memory and the next request will be forwarded to the API.

Next: Throttled Request Queue