That extension is on the right track to what we would need, unfortunately it only works for groovy.
I wasn't thinking that it would have to be at the JVM level but maybe at the rendering context level or context level in general? The context could then can keep track of how deeply nested the inclusions are as well as keep track of how long the request has been running. These limits can then be checked at critical times while rendering is occurring and then throw an Exception to abort the process should a limit be broken. It wouldn't necessarily have to guarantee 100% accuracy in the first iteration of the feature, but a best effort could be good for some protection. -- View this message in context: http://xwiki.475771.n2.nabble.com/Page-Complexity-limiter-tp7602880p7602882.html Sent from the XWiki- Dev mailing list archive at Nabble.com.
