- From: Alex Muir <alex.g.muir@gmail.com>
- Date: Mon, 14 Mar 2011 16:19:40 +0000
- To: vojtech.toman@emc.com
- Cc: xproc-dev@w3.org
- Message-ID: <AANLkTin-EuYrazsnYxjqPpfo7VjipHnYL9k40v8rkuLo@mail.gmail.com>
"In some situations it doesn’t matter, but you typically want to prevent the XProc processor from “randomly” deciding the execution order of the steps in the pipeline." Interesting.. What is the benefit to allow XProc processor to randomly decide the execution order of the steps and when does that happen in practice? I read previously http://norman.walsh.name/2009/03/26/xprocWithXProc which states in a section that "But if you look at the store and exec steps in the preceding pipeline, you'll see that there are no connections between them. Effectively, we have a pipeline with two independent sub-pipelines. ... As a result, there's no dependency between the store and exec steps. The pipeline processor can execute them in any order, even in parallel. But the correct result requires that the p:store step be executed before p:exec." I wonder why one wouldn't generally want the steps to execute one after the other unless specified otherwise in someway by the script to for example execute in parallel or to execute and not wait? Regards Alex
Received on Monday, 14 March 2011 16:20:24 UTC