Suggestion: GroovyScriptCompiler o.s., and add comment in GCL documentation "If you want concurrency performance, ... to compile Groovy scripts in your application, use GroovyScriptCompiler."Make GCL functionality private, or at least add the same comment there.
Rationale: From what I have read here, Groovy users seem to follow the same path of reasoning, landing at GCL as the place they expect this to work. GCL looks quite low level from the outside, so this makes sense to me.GroovyShell is not where I would look for this, since I would assume it to be too heavyweight a class, with a lot of functionality I do not need/want. mg10c -------- Ursprüngliche Nachricht --------Von: Jochen Theodorou <blackd...@gmx.org> Datum: 24.02.18 12:06 (GMT+01:00) An: dev@groovy.apache.org Betreff: Re: Thread contention on GroovyClassLoader sourceCache On 24.02.2018 07:14, Daniel Sun wrote: > Hi Jochen, > > As a Groovy user, I prefer higher level API, e.g. `GroovyShell`, > `GroovyClassLoader` ;-) This kind of functionality can be in a higher API of course, but I think GCL needs to be split instead of having another "mode". I think GroovyShell would be a better place for this. Or maybe a another GroovyShell bye Jochen
