[jira] [Updated] (SLING-4016) Allow to override sling.max.calls per request
[ https://issues.apache.org/jira/browse/SLING-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-4016: - Affects Version/s: Engine 2.3.6 Fix Version/s: Engine 2.3.8 Allow to override sling.max.calls per request - Key: SLING-4016 URL: https://issues.apache.org/jira/browse/SLING-4016 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.3.6 Reporter: Alexandre Capt Assignee: Felix Meschberger Fix For: Engine 2.3.8 Attachments: SLING-4016_-_Allow_to_override_sling_max_calls_per_request.patch sling.max.calls limits the number of scripts that can be included. In some cases and especially for large trees, this number must be increased. But increasing for all the request is a risk. It would be really useful and needed in some cases to allow a override for certain under control requests. An easy way would be via a request attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4016) Allow to override sling.max.calls per request
[ https://issues.apache.org/jira/browse/SLING-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandre Capt updated SLING-4016: -- Attachment: SLING-4016_-_Allow_to_override_sling_max_calls_per_request.patch Here is a patch that implements the described feature request. Allows to add a request attribute named sling.max.calls in order to control the max calls. Value can be -1 for infinite or integer value to change the max for the request. Allow to override sling.max.calls per request - Key: SLING-4016 URL: https://issues.apache.org/jira/browse/SLING-4016 Project: Sling Issue Type: Improvement Components: Engine Reporter: Alexandre Capt Attachments: SLING-4016_-_Allow_to_override_sling_max_calls_per_request.patch sling.max.calls limits the number of scripts that can be included. In some cases and especially for large trees, this number must be increased. But increasing for all the request is a risk. It would be really useful and needed in some cases to allow a override for certain under control requests. An easy way would be via a request attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
