From 2ea880ce2cdb192f9d91d8902d4c70b312798a00 Mon Sep 17 00:00:00 2001
From: Raul Ochoa <rochoaf@gmail.com>
Date: Tue, 7 Apr 2015 11:09:35 +0200
Subject: [PATCH] cacheOnTimeout only for mapnik renderer it does not make
 sense to have that as a general feature

---
 config/environments/development.js.example | 3 ---
 config/environments/production.js.example  | 3 ---
 config/environments/staging.js.example     | 3 ---
 config/environments/test.js.example        | 3 ---
 4 files changed, 12 deletions(-)

diff --git a/config/environments/development.js.example b/config/environments/development.js.example
index eca061b5..7b7866b1 100644
--- a/config/environments/development.js.example
+++ b/config/environments/development.js.example
@@ -196,9 +196,6 @@ var config = {
 
     // Use this as a feature flags enabling/disabling mechanism
     ,enabledFeatures: {
-        // whether a timed out render request should be cached in memory after is computed or not
-        // beware keeping it will grow up the memory usage
-        cacheOnTimeout: false,
         // whether it should intercept tile render errors an act based on them, enabled by default.
         onTileErrorStrategy: true,
         // whether the affected tables for a given SQL must query directly postgresql or use the SQL API
diff --git a/config/environments/production.js.example b/config/environments/production.js.example
index 7cecf67f..72fae68b 100644
--- a/config/environments/production.js.example
+++ b/config/environments/production.js.example
@@ -196,9 +196,6 @@ var config = {
 
     // Use this as a feature flags enabling/disabling mechanism
     ,enabledFeatures: {
-        // whether a timed out render request should be cached in memory after is computed or not
-        // beware keeping it will grow up the memory usage
-        cacheOnTimeout: false,
         // whether it should intercept tile render errors an act based on them, enabled by default.
         onTileErrorStrategy: true,
         // whether the affected tables for a given SQL must query directly postgresql or use the SQL API
diff --git a/config/environments/staging.js.example b/config/environments/staging.js.example
index 32e1c581..242890f6 100644
--- a/config/environments/staging.js.example
+++ b/config/environments/staging.js.example
@@ -196,9 +196,6 @@ var config = {
 
     // Use this as a feature flags enabling/disabling mechanism
     ,enabledFeatures: {
-        // whether a timed out render request should be cached in memory after is computed or not
-        // beware keeping it will grow up the memory usage
-        cacheOnTimeout: false,
         // whether it should intercept tile render errors an act based on them, enabled by default.
         onTileErrorStrategy: true,
         // whether the affected tables for a given SQL must query directly postgresql or use the SQL API
diff --git a/config/environments/test.js.example b/config/environments/test.js.example
index 80f2c6b5..de03dc7f 100644
--- a/config/environments/test.js.example
+++ b/config/environments/test.js.example
@@ -192,9 +192,6 @@ var config = {
 
     // Use this as a feature flags enabling/disabling mechanism
     ,enabledFeatures: {
-        // whether a timed out render request should be cached in memory after is computed or not
-        // beware keeping it will grow up the memory usage
-        cacheOnTimeout: false,
         // whether it should intercept tile render errors an act based on them, enabled by default.
         onTileErrorStrategy: true,
         // whether the affected tables for a given SQL must query directly postgresql or use the SQL API