Le 4 oct. 05, à 02:15, Bruyn Bill a écrit :
...<!-- provide reusable data access / collection mechanisms --> Pipeline 1: Get some data from a database and represent result as XML Pipeline 2: Present the user with some series of forms, do stuff, and represent result as XMLPipeline 3: Present the user with some other forms, do other stuff, andrepresent result as XML<!-- and reference them --> Pipeline 4: get xml result from pipeline 2 Pipeline 5: get xml result from pipelines 1 and 2 Pipeline 6: get xml result from pipelines 2 and 3..
IIUC steps 4,5,6 come later than 1,2,3, so the output of 1,2,3 should be saved for a while?
If so, the easiest that comes to mind would be to create a temporary directory (with a unique ID tied to the user's session via a flow variable), and store the output of 1,2,3 there for later use. Think REST: 1,2,3 create resources that are referenced later on.
You could also store the results of 1,2,3 in the user's session (as DOM objects), but depending on the amount of data and load it might be too heavy.
-Bertrand
smime.p7s
Description: S/MIME cryptographic signature
