On 09/11/2011 15:22, Michael Bane wrote: Hello
> I went down the Soaplab2 route so would be interested in hearing comparisons. In Soaplab2 it creates a set of webservices that wrap the calling of the tool. Those webservices are then hosted, for example, in Apache Tomcat. The webservices are, by default, callable by anyone. The tool service allows you to call a set of commands in a workflow, with the commands being run locally or remotely. If you run them remotely then (at present) the remote host is contacted using ssh. The tool services are (by virtue of ssh), by default, secured. With Soaplab (and other web services such as WSDL and REST), the data is transferred to and from the machine where the service runs. This happens even if the data is downloaded only to be uploaded as part of another call to the same machine. (This is why we recommend that references to data, rather than the actual data, are transferred.) For a tool service, the data is kept on the service host until it needs to be transferred to another machine. This means, if you are making several calls to services on machine X, then there will be greatly reduced downloading/uploading of data. The tool service is currently quite new and so can, depending upon what you are doing, be "fragile". > Thanks, M > Michael Bane > University of Manchester > http://www.rcs.manchester.ac.uk/mkbane > @mkbane_mcr Alan ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/
