cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <>
Subject RE: Why is FlowInterpreter SingleThreaded?
Date Tue, 21 Oct 2003 06:29:11 GMT
Sylvain Wallez wrote:
> After looking carefully, the interpreter must be SingleThreaded, even if 
> thread safe...
> This is because although an intepreter can handle concurrent requests, 
> each sitemap must have a different instance, since the interpreter holds 
> the scripts defined in a <map:flow> statement.
> So if the interpreter is made ThreadSafe, a unique instance will exist 
> for the whole system, and will mix all script definitions and script 
> global variables. Making it SingleThreaded ensures each sitemap will 
> have its own instance. It seems hacky, but I don't see what other means 
> we have to achieve this...
Ok, I understand that; so we *could* make it Poolable then, right?
This is not a hugh issue anyway, but I fear that people might copy the
code and use SingleThreaded in other places where it does matter.


View raw message