> If I implement the service asynchronously, i.e., get rid of waitfor(), > the next service in the pipeline will suffer because the input might > have not been returned by its predecessor.
In the asynchronous case you should call your services differently. One way of calling asynchronous services can be seen in the following workflow (see the box EBI_ClustalW2_poll_job and its relation with the run call and the get result calls) http://www.myexperiment.org/workflows/203 Regards, Mahmut ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/
