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
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
Ugo Cei wrote:
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
Christopher Oliver wrote:
Again I know nothing about Avalon, but there seems to be some
conceptual confusion between Stateless and ThreadSafe. Stateless
objects are of course thread-safe but stateful objects may be also. A
container that automatically turns a ThreadSafe component into a
Christopher Oliver wrote:
Again I know nothing about Avalon, but there seems to be some conceptual
confusion between Stateless and ThreadSafe. Stateless objects are of
course thread-safe but stateful objects may be also. A container that
automatically turns a ThreadSafe component into a
Christopher Oliver wrote:
I think SingleThreaded is rather misleading in this case. I know
nothing about Avalon but from my experience it appears one flow
interpreter is created per sitemap. However, this instance is definitely
accessed by many threads concurrently. I had to put my own
Carsten Ziegeler wrote:
Christopher Oliver wrote:
I think SingleThreaded is rather misleading in this case. I know
nothing about Avalon but from my experience it appears one flow
interpreter is created per sitemap. However, this instance is definitely
accessed by many threads concurrently.
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
Torsten Curdt 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
snip/
This means that the interpreter must externalize its state (compiled
scripts and global scope) in an object stored in the treeprocessor for a
sitemap (in the FlowNode).
yes
Or another solution is to change Interpreter into InterpreterFactory:
the state mentioned above would then be the
Torsten Curdt wrote:
snip/
This means that the interpreter must externalize its state
(compiled scripts and global scope) in an object stored in the
treeprocessor for a sitemap (in the FlowNode).
yes
Or another solution is to change Interpreter into InterpreterFactory:
the state mentioned
huh? do you mean there is exactly one interpreter for a specific state
accessable through the factory? please explain :)
Let's explain it in (pseudo-)code:
FlowNode.java:
// the flow interpreter for this sitemap
private Interpreter interpreter;
public void initialize() {
IntepreterFactory
Torsten Curdt wrote:
huh? do you mean there is exactly one interpreter for a specific
state accessable through the factory? please explain :)
Let's explain it in (pseudo-)code:
FlowNode.java:
// the flow interpreter for this sitemap
private Interpreter interpreter;
public void
Again I know nothing about Avalon, but there seems to be some conceptual
confusion between Stateless and ThreadSafe. Stateless objects are of
course thread-safe but stateful objects may be also. A container that
automatically turns a ThreadSafe component into a singleton seems
broken to me.
Just curious for the reason why o.a.c.c.flow.AbstractInterpreter
implements SingleThreaded (and therefore the flow interpreter as
well)?
SingleThreaded means that for each lookup a new instance is
created.
Carsten
I think SingleThreaded is rather misleading in this case. I know
nothing about Avalon but from my experience it appears one flow
interpreter is created per sitemap. However, this instance is definitely
accessed by many threads concurrently. I had to put my own
synchronization code into
16 matches
Mail list logo
