On 8/28/06, Omar Adobati <[EMAIL PROTECTED]> wrote:
...suppose I want to aggregate more than one action or more then one transformer. I could have back more than one "response" (success or error) form each one. Could I aggregate them in one "result page" using aggregate (maybe in collaboration with cocoon protocol)?..
sure, that's how you'd do it: use the cocoon protocol and transform the results to status information on your HTML page.
...If each "job" take different time to be executed will I have the "result page" at the end of the last (longer??) job?..
Using aggregates, yes, in principle. It depends on how "streamable" the rest of your pipeline is, and getting the full response will wait on all aggregates.
...(if yes, maybe with some ajax code will be possible to have my "result page" dynamically build with results from each job)...
That's a way of doing it: have the pipelines start the "long" jobs, and use ajax + other pipelines to get their status later, once the page is loaded.
...Same questions for the flowscript too...
Flowscript will give you more flexibility w.r.t multi-threading and precise control of what's happening. If your problem is actually sending email, the best way by far is to consider some queuing mechanism, as you have no way of knowing how much time it will take to actually send an email. IIRC, Daisy queues outgoing emails in its database (or using JMS?), you might want to look at how they do it. But, depending on your peak load, simpler options might be good enough. -Bertrand --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
