I have a use case where we have quite complex node structure hierarchy. On the first request iterate all the nodes of the structure and cache what ever is required.
So what is happening is that for the first render, the default sling max calls fails me I start getting too many calls exception[0]. I know this configuration is dangerous to play with but what I want to do is check the current value of the sling.max.calls. If the value is less that what I expect, then set it to my estimated value. I just don't want to blindly set some value in request attribute. Only when I see that the current system wide value is less that I would need for this call, then only I want to set a new value in the request attribute. Now this configuration ( configurations of Sling Main Servlet ) are not exposed in request but rather kept safe in a internal object RequestData [1] . Would it be fine if I submit a patch exposing it like a request attribute ? Or are there better way to achieve my use case ? Thanks, Mandeep Gandhi [0] - https://sling.apache.org/apidocs/sling7/org/apache/sling/api/request/TooManyCallsException.html#TooManyCallsException-java.lang.String- [1] - https://github.com/apache/sling/blob/trunk/bundles/engine/src/main/java/org/apache/sling/engine/impl/request/RequestData.java
