Paul Fisher wrote: > Ok. > > How about autosave *and *recovery. > > Microsoft Word creates a temporary file that is purged from the system > (if no errors are reported) when the application closes. If a fault > occurs, the temp file can be used to recover the document at the last > autosave checkpoint. > > Substitute document for workflow. > > Taverna would autosave the workflow say every 30 minutes, as a temporary > file. If the workbench crashes, this could be used to recover the > workflow. If I closed the workbench, the temp file could then be deleted.
I'd actually just save on every change to the workflow, do it in the background to avoid interrupting the UI (obvious anyway but never hurts to say!). If you also save the edits alongside it you're good to go when you restart the workbench. Don't think of it as saving the workflow, think of it as saving the state of the workbench session. Tom (giving away features of his new workbench design, one at a time....) ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ taverna-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/taverna-users Documentation: http://www.mygrid.org.uk/usermanual1.7/ FAQ: http://www.mygrid.org.uk/wiki/Mygrid/TavernaFaq Biological Services: http://www.mygrid.org.uk/wiki/Mygrid/BiologicalWebServices
