> the concurrency issue is currently entangled with the controller discussion, because sequential processing is enforced
how so? if you invoke N actions they don't run sequentially - each is its own activation, unless you actually invokes a sequence. Can you clarify this point? -r
